Connection factory creation problem on Solaris

I am trying to create a QueueConnectionFactory using imqobjmr utility with the following input file...
version=2.0
cmdtype=add
obj.type=qf
obj.lookupName=MyQueueConnectionFactory
objstore.attrs.java.naming.factory.initial= com.sun.jndi.fscontext.RefFSContextFactory
objstore.attrs.java.naming.provider.url= file:///local/MessageQueueObjects/
and it generates the following error...
Error [A3050]: imqobjmgr does not recognize the value of java.naming.factory.initial property.
is it something related to not finding the proper jar file, if yes how do i do that...
please help me in this regard...
thanks a lot in adavnce
Hugo

Hi Hugo,
What version of MQ are you using ?
I just tried using MQ 3.0.1 and it works fine.
I noticed you had some spaces between the '=' and the
value of the factory initial and provider url but even with that
my tests work (on Solaris).
imqobjmgr usually lists all the values for the object it will
add and the values for the JNDI attributes so you should
see what the 'bad' value for java.naming.factory.initial is.
Can you post more output from imqobjmgr - specifically the
part that shows the values for the JNDI attrs ?
With regards to jar files, can you also show us the output
of imqobjmgr -v ? This shows CLASSPATH, which may
give us some idea if that is the issue.
regards,
-isa

Similar Messages

Problem with transacted JMS connection factory and transaction timeouts

          We encountered an interesting problem using transacted JMS connection factories.
          An EJB starts a container managed transaction and tries to validate a credit card
          before creating some information to a database for the user, in case of success
          an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          duration is about the same as the transactions timeout (in this case the default
          30 seconds) sometimes the database inserts is committed but the JMS insert is
          rollbacked. How can this be?
          If the authorization duration is much longer than 30 seconds everything works
          fine (both database and JMS inserts rollbacked), the same is true if a rollback
          is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          if the duration is approximately the same as the transaction timeout, it appears
          that the database insert is not timeouted but the JMS insert is. How can this
          be if they are both participating in the same transaction.
          The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          configure our own factory with user transactions enabled.
          Any help appreciated!


Tomas Granö wrote:
          > We encountered an interesting problem using transacted JMS connection factories.
          > An EJB starts a container managed transaction and tries to validate a credit card
          > before creating some information to a database for the user, in case of success
          > an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          > duration is about the same as the transactions timeout (in this case the default
          > 30 seconds) sometimes the database inserts is committed but the JMS insert is
          > rollbacked. How can this be?
          It should not be.
          >
          > If the authorization duration is much longer than 30 seconds everything works
          > fine (both database and JMS inserts rollbacked), the same is true if a rollback
          > is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          > if the duration is approximately the same as the transaction timeout, it appears
          > that the database insert is not timeouted but the JMS insert is. How can this
          > be if they are both participating in the same transaction.
          >
          > The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          > is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          > configure our own factory with user transactions enabled.
          >
          > Any help appreciated!
          Make sure that your session is not "transacted". In other words,
          the first parameter to createSession() must be false. There is an
          unfortunate name re-use here. If a session is "transacted", it
          maintains an independent "inner transaction" independent of the
          outer transaction. From the above description, it seems unlikely
          that your application has this wrong, as you say that
          "setRollbackOnly" works - but please check anyway.
          Make sure that you are using a true XA capable driver and database
          (XA "emulation" may not suffice)
          Beyond the above, I do not see what can be going wrong. You
          may want to try posting to the transactions and jdbc newsgroups. Note
          that JMS is appears to be exhibiting the correct behavior, but the
          JDBC operation is not. The JDBC operation appears to have
          its timeout independent of the transaction monitor's timeout.
          Tom

Problem in datasource and connection factory.

I am using a connection factory to make connections to the database.
First I create a connection pool then i created a datasource and finally i used the JNDI Location name which i used inside the BPEL to create a connection factory.
Does this activity requires a restart of server. I am getting the following error.
file:/software/product/10.1.3.3.0/bpel/domains/default/tmp/.bpel_IRobo_Workflow1_1.0_e580208857197172fe72bbfca5d9d8b6.tmp/fr_jumper_info.wsdl [ fr_jumper_info_ptt::fr_jumper_info(InputParameters) ] - WSIF JCA Execute of operation 'fr_jumper_info' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: VDMT_IROBO_DATASOURCE not found]
; nested exception is:
     ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: VDMT_IROBO_DATASOURCE not found]
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-7060] (Oracle TopLink - 10g Release 3 (10.1.3.3.0) (Build 070608)): oracle.toplink.exceptions.ValidationException
Exception Description: Cannot acquire data source [VDMT_IROBO_DATASOURCE].
Internal Exception: javax.naming.NameNotFoundException: VDMT_IROBO_DATASOURCE not found.
</summary>
</part>
-<part name="detail">
<detail>
Exception Description: Cannot acquire data source [VDMT_IROBO_DATASOURCE].
Internal Exception: javax.naming.NameNotFoundException: VDMT_IROBO_DATASOURCE not found
</detailException Description: Cannot acquire data source [VDMT_IROBO_DATASOURCE].
Internal Exception: javax.naming.NameNotFoundException: VDMT_IROBO_DATASOURCE not found
</detail

Hi James
I have created the data source and i can find it in the path C:\product\10.1.3.1\OracleAS_1\j2ee\home\config\data-sources.xml
<managed-data-source connection-pool-name="IRoboConnectionPool" jndi-name="jdbc/VDMT_IROBO_DATASOURCE" name="VDMT_IROBO_DATASOURCE"/>
And in C:\product\10.1.3.1\OracleAS_1\j2ee\home\application-deployments\default\DbAdapter\oc4j-ra.xml i can see
     <connector-factory location="eis/DB/VDMT_IROBO" connector-name="Database Adapter">
          <config-property name="xADataSourceName" value="jdbc/VDMT_IROBO_DATASOURCE"/>
          <config-property name="dataSourceName" value="VDMT_IROBO_DATASOURCE"/>
          <config-property name="platformClassName" value="oracle.toplink.platform.database.Oracle9Platform"/>
          <config-property name="usesNativeSequencing" value="true"/>
          <config-property name="sequencePreallocationSize" value="50"/>
          <config-property name="defaultNChar" value="false"/>
          <config-property name="usesBatchWriting" value="true"/>
          <connection-pooling use="none">
          </connection-pooling>
          <security-config use="none">
          </security-config>
     </connector-factory>
You have said I have given the name for dataSourceName incorrectly , what value should we give I dont know that I thought it is a user defined value.

Messaging Bridge/Resource adapter problem on Solaris?

          Has anyone successfully used the supplied resource adapter and messaging bridge
          on Solaris? We seem to have problems getting the resource adapter to be bound
          properly. After creating a connector through the admin console (using any of the
          weblogic supplied jms-*-adp.rar files) the element shows up in the JNDI tree but
          has no object information associated with it - which I assume means it is not
          bound. The following error shows up in the weblogic log file:
          ####<Jan 24, 2003 6:28:03 PM CST> <Error> <Connector> <fssun02> <AdminServer>
          <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <kernel identity>
          <> <190004> <ManagedConnectionFactory not found for jndiName eis/jms/WLSConnectionFactoryJNDINoTX.>
          We are using WL 7.0.1.0 and Solaris 2.8 (8). With the same configuration on Win
          2K everything works properly. Classpath's etc all seem to be correct. Any ideas?
          thanks,


I finally got my Messaging Bridge (Tibco to a WLS Cluster) to work. See my post 3 messages before yours - to which no-one responded... :-(
          So here goes with my suggestion based on what I have done.
          1. Create a Distributed Destination for the WLS queue and "auto deploy" it your cluster. (Read the manual on how to do that, it is quite straightforward).
          2. In the Local Bridge Destination, put :
          Connection URL - nothing
          Initial Context Factory - weblogic.jndi.WLInitialContextFactory
          Connection Factory JNDI Name - <your JMS conection factory name>
          Destination JNDI Name - <the JNDI name given to the Distributed Destination>.
          I hope that works.
          Andy

Dynamic Connection Pool Creation Failing in a cluster

Hi,
I am trying to create a connection pool in a clustered environment. This connection
pool is created lazily behind a Stateless Session Bean. We first attempt to determine
whether, the connection pool exists using JdbcServices.poolExists(someName), and
create it if it does not exist. A failure occurs on creation because it looks
like the connection pool might have been created by a bean on a different weblogic
VM instance. Is there any way to dynamically create a connection pool and make
it visible to the whole cluster? Thanks in advance for any help. Michael Dolbear
Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence of connection pool
Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection pool ContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException: weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
at weblogic.management.internal.Helper.createMBean(Helper.java:376)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
at weblogic.management.internal.Helper.createMBean(Helper.java:383)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
        at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
        at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
        at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
        at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
        at weblogic.management.internal.Helper.createMBean(Helper.java:376)
        at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
        at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
        at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
        at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
        at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
        at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:47
2)
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:727
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:709
at com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.createConne
ctionPool(ConnectionPoolCreator.java:82)
at com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnectionPoo
lIfNonExistent(DataStoreRepository.java:211)
at com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createConnec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.create
ConnectionPoolIfNeeded(Unknown Source)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.getIma
ge(Unknown Source)
at com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unknown
Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescriptio
n.java:181)
at com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.java:7
9)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.java:
186)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invoke(Ser
viceBean_bjedmi_EOImpl.java:37)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSkel.inv
oke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence of connection
pool Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection pool ContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException: weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
at weblogic.management.internal.Helper.createMBean(Helper.java:376)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
at weblogic.management.internal.Helper.createMBean(Helper.java:383)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
        at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
        at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
        at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
        at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
        at weblogic.management.internal.Helper.createMBean(Helper.java:376)
        at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
        at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
        at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
        at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
        at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
        at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:47
2)
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:727
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:709
at com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.createConne
ctionPool(ConnectionPoolCreator.java:82)
at com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnectionPoo
lIfNonExistent(DataStoreRepository.java:211)
at com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createConnec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.create
ConnectionPoolIfNeeded(Unknown Source)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.getIma
ge(Unknown Source)
at com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unknown
Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescriptio
n.java:181)
at com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.java:7
9)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.java:
186)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invoke(Ser
viceBean_bjedmi_EOImpl.java:37)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSkel.inv
oke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

The only way to do it is using MBeans. You could search this newsgroup
for "JDBCConnectionPoolMBean" to get an idea of how it could be done.
Slava
P.S. http://search.bea.com/weblogic/gonews
"Mark Mortensen" <[email protected]> wrote in message
news:[email protected]...
>
Slava,
I am working with Mike on this issue and wanted to add some moreclarifications.
We have a two server cluster where one of the EJB's on one of the Managedservers
creates the connection pool. The problem comes in when a request comes tothe
second server in the cluster. The connection pool is created by the firstserver
but it is only assigned to the first server in the targets section on theconsole.
It isn't assigned to the cluster. Is there a way to programmaticallyassign the
pool to the cluster instead of just the server that created the pool?
-Mark
"Michael Dolear" <[email protected]> wrote:
Hi Slava,
Here is what I am doing. The code is spread across a couple of classes.
I am using
what was described in BEA's doc on dynamic connection pool creation.
I didn't
see anything about MBean apis required:
* Dynamically create a connection pool using
aConnectionPoolProperties.
Please
see ConnectionPoolCreator
* for the required properties that must be sent in.
* @param aConnectionPoolProperties
public synchronized void createConnectionPoolIfNonExistent(Properties
aConnectionPoolProperties)
throwsPersistenceFrameworkInitializationException
ConnectionPoolCreator tempPoolCreator;
Pool tempPool;
tempPoolCreator = new ConnectionPoolCreator();
tempPool =tempPoolCreator.getConnectionPool(aConnectionPoolProperties);
if (tempPool == null)
tempPoolCreator.createConnectionPool(aConnectionPoolProperties);
>>
* Create Connection pool given the properties that I have beenconfigured
with
* @return Pool
public Pool createConnectionPool(Properties aConnectionProperties)
throwsPersistenceFrameworkInitializationException
JdbcServices tempServices;
try
tempServices = this.lookupJdbcServices();
tempServices.createPool(aConnectionProperties);
returntempServices.getPool(aConnectionProperties.getProperty(CONNECTION_POOL_NAME)
catch (Exception e)
PersistenceFrameworkUtils.logException(e);
throw newPersistenceFrameworkInitializationException(e.getMessage());
* Answer a connectionPool or null.
* @return Pool
public Pool getConnectionPool(Properties aConnectionProperties)
throwsPersistenceFrameworkInitializationException
JdbcServices tempServices;
try
tempServices = this.lookupJdbcServices();
if (tempServices.poolExists(
aConnectionProperties.getProperty(CONNECTION_POOL_NAME)))
return tempServices.getPool(
aConnectionProperties.getProperty(CONNECTION_POOL_NAME));
else
return null;
catch (Exception e)
PersistenceFrameworkUtils.logException(e);
throw
newPersistenceFrameworkInitializationException(e.getMessage());
"Slava Imeshev" <[email protected]> wrote:
Hi Michael,
Could you show us the code? Without looking at the code
I can only say that JdbcServices.poolExists(someName)
returns true only in case the pool is up and running.
If the connection pool MBean was created but not assigned
a target, subsequent tries to create it would fail.
Regards,
Slava Imeshev
"Michael Dolbear" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am trying to create a connection pool in a clustered environment.This
connection
pool is created lazily behind a Stateless Session Bean. We first
attempt
to determine
whether, the connection pool exists usingJdbcServices.poolExists(someName), and
create it if it does not exist. A failure occurs on creation becauseit
looks
like the connection pool might have been created by a bean on a
different
weblogic
VM instance. Is there any way to dynamically create a connection pooland
make
it visible to the whole cluster? Thanks in advance for any help.
Michael
Dolbear
Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence ofconnection pool
Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection poolContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException:weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
atweblogic.management.internal.Helper.createMBean(Helper.java:383)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at
weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.ja
va
:47
2)
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
727
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
709
at
com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.create
Co
nne
ctionPool(ConnectionPoolCreator.java:82)
at
com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnecti
on
Poo
lIfNonExistent(DataStoreRepository.java:211)
at
com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createC
on
nec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.c
re
ate
ConnectionPoolIfNeeded(Unknown Source)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.g
et
Ima
ge(Unknown Source)
at
com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unk
no
wn
Source)
at java.lang.reflect.Method.invoke(Native Method)
at
com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescr
ip
tio
n.java:181)
at
com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.j
av
a:7
9)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.
ja
va:
186)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invok
e(
Ser
viceBean_bjedmi_EOImpl.java:37)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSke
l.
inv
oke(Unknown Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.ja
va
:93
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence ofconnection
pool Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection poolContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException:weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
atweblogic.management.internal.Helper.createMBean(Helper.java:383)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at
weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.ja
va
:47
2)
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
727
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
709
at
com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.create
Co
nne
ctionPool(ConnectionPoolCreator.java:82)
at
com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnecti
on
Poo
lIfNonExistent(DataStoreRepository.java:211)
at
com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createC
on
nec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.c
re
ate
ConnectionPoolIfNeeded(Unknown Source)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.g
et
Ima
ge(Unknown Source)
at
com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unk
no
wn
Source)
at java.lang.reflect.Method.invoke(Native Method)
at
com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescr
ip
tio
n.java:181)
at
com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.j
av
a:7
9)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.
ja
va:
186)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invok
e(
Ser
viceBean_bjedmi_EOImpl.java:37)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSke
l.
inv
oke(Unknown Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.ja
va
:93
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Metainit/striping problem on Solaris 9

We are trying to deploy the Apple XServe RAIDS to customers running Solaris 9. The issue is that Solaris 9 will not recognize a device/LUN that is > 2TB. (No problem with Solaris 10) In trying to solve this problem, we sliced a 7 disk (4.09 TB) RAID into 3 slices. This presents three 1.36TB disks to the Solaris system. Basically, we have 6 disks being presented across both controllers to Solaris. They are direct connected from the XServe to a dual port QLogic HBA. The problem comes in when you try to create a stripe/concatenation across the logical devices being presented. (The disks are being presented on C4 and C5)
Results from a format AFTER I split both 7 disk RAID5s into 3 slices.
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@1,0
2. c1t2d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@2,0
3. c1t3d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@3,0
4. c4t600039300001F461d0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,0
5. c4t600039300001F461d1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,1
6. c4t600039300001F461d2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,2
7. c5t600039300001F2ECd0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,0
8. c5t600039300001F2ECd1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,1
9. c5t600039300001F2ECd2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,2
Specify disk (enter its number):
Results of the cfgadm command. You will see there three logical devices presented to each controller. Six disks.
cfgadm -al -o showFCPdev
Ap_Id Type Receptacle Occupant Condition
c4 fc-private connected configured unknown
c4::600039300001f461,0 disk connected configured unknown
c4::600039300001f461,1 disk connected configured unknown
c4::600039300001f461,2 disk connected configured unknown
c5 fc-private connected configured unknown
c5::600039300001f2ec,0 disk connected configured unknown
c5::600039300001f2ec,1 disk connected configured unknown
c5::600039300001f2ec,2 disk connected configured unknown
Trying to initialize a 6 device stripe via Solaris Volume Manager (AKA disksuite)
metainit -f d77 6 1 c4t600039300001F461d0s0 1 c4t600039300001F461d1s0 1 c4t600039300001F461d2s0 1 c5t600039300001F2ECd0s0 1 c5t600039300001F2ECd1s0 1 c5t600039300001F2ECd2s0
I receive the following error:
metainit: hostname: c4t600039300001F461d1s0: overlaps with device in d77
I tried to do a work around where I create three striped devices then concatenate them:
Creating the first 2 device stripe across controllers c4 and c5 (1 device each)
metainit -f d77 2 1 c4t600039300001F461d0s0 1 c5t600039300001F2ECd0s0
I was able to create the first metadevice d77 using one logical LUN from each controller.
When I tried to create a second metadevice across the controllers: (Using d1 from each controller)
metainit -f d78 2 1 c4t600039300001F461d1s0 1 c5t600039300001F2ECd1s0
metainit: hostneme: c4t600039300001F461d1s0: overlaps with device in d77
I received the same error.
In doing some reaearch, it seems the problem is due to a problem with the disk duplication process, disk device IDs stored on the disks are not unique. I was curious if this is the problem that Apple presents the split disks with the SAME diskid? Has anybody else successfully created stripes (due to a LUN size limit) across the disk successfully on a Solaris system?

I contacted Sun and here is an explination from them. I also noticed when I queried the Xserver RAIDS, there were no serial numbers.
Solaris 9 can support a 16Tb filesystem, but there is a scsi limitation on the device of 2Tb. So you are stuck with striping together several smaller devices if you want a single filesystem above 2Tb.
The problem you are having when metainit reports an overlap comes from the way Solaris Volume Manager identifies devices. The portion of the scsi inquiry that is returned is always unique when Sun firmware is involved, but in your case is not unique.
You may be able to make use of the appended infodoc to avoid this problem. I see no evidence of our having tested this with your particular scenario, but it has been successful in similar cases.
You might also inquire of whoever supports your storage device whether a mode is supported whereby the device's inquiry strings can be made unique.
Here is the steps he wanted me to take and the results. I still can not get the Xserve RAIDS to generate a unique device id:
Step 1
Determine the vendor and product strings. You can run these commands:
# netstat -k | grep -i vendor
# netstat -k | grep -i product
netstat -k | grep -i vendor
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
grep -i product
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
or you can run
# format -e
then select scsi, then inquiry.
scsi> inq
Inquiry:
00 00 05 12 5b 00 00 02 41 50 50 4c 45 20 20 20 ....[...APPLE
58 73 65 72 76 65 20 52 41 49 44 20 20 20 20 20 Xserve RAID
31 2e 35 31 63 00 00 00 00 00 00 00 00 00 00 00 1.51c...........
00 00 00 00 00 00 00 00 00 00 0d 40 0d a0 0e 20 ...........@...
0d 80 09 00 0a 00 00 20 00 00 00 20 20 20 20 20 ....... ...
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
Vendor: APPLE
Product: Xserve RAID
Revision: 1.51
Removable media: no
Device type: 0
ISO version: 0
ECMA version: 0
ANSI version: 5
Async event notification: no
Terminate i/o process msg: no
Response data format: 2
Additional length: 91
Relative addressing: no
32 bit transfers: no
16 bit transfers: no
Synchronous transfers: no
Linked commands: no
Command queueing: yes
Soft reset option: no
Step 2
Add an entry in the file '/kernel/drv/sd.conf'.
sd-config-list=
"APPLE Xserve RAID ", "AppleRAID";
AppleRAID=1,0x8,0,0,0,0,0;
Step 3 Reboot.
Step 4 Check with SUNWexplo.
[email protected]:[/opt/SUNWexplo/bin] (8)# ./diskinfo.sparc
/dev/rdsk/c0t0d0s2: Device busy
AVAILABLE SCSI DEVICES:
Location Vendor Product Rev Serial #
c1t0d0 COMPAQ BD036863AC HPB5 B2FT4HMM
c1t1d0 SEAGATE ST336607LSUN36G 0507 0349A66VKQ
c1t2d0 SEAGATE ST373307LSUN72G 0507 0417B7C9ZC
c1t3d0 SEAGATE ST373307LSUN72G 0507 0425B7LV5Q
c4t600039300001F461d0 APPLE Xserve RAID 151 c
c4t600039300001F461d1 APPLE Xserve RAID 151 c
c4t600039300001F461d2 APPLE Xserve RAID 151 c
c5t600039300001F2ECd0 APPLE Xserve RAID 151 c
c5t600039300001F2ECd1 APPLE Xserve RAID 151 c
As you will notice, there are no serial numbers in this command or netstat -k | grep -i product commands.

Enhanced Storage Problem in Solaris Management Console Started in XManager

I have Sun Fire 480 with solaris 5.9 installed on it. I use XManager 1.3.9 on windows 2000 workstation to connect to it and launch Solaris Management Console (smc). After starting smc I point to Management Tools -> This Computer (sf480dbs) -> Storage -> Enhanced Storage. At that moment Log In dialog appears and I give root user name and password. After a few seconds SMC disappears (exits). If I look at CDE Error log there is the following exception
Thu Jul 31 21:00:36 2003 (/usr/dt/bin/dtexec) /usr/sbin/smc
Exception while creating engine named com.sun.java.help.search.DefaultSearchEngine for view: javax.help.SearchView@4db52b
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at javax.help.search.MergingSearchEngine.makeEngine(MergingSearchEngine.java:148)
at javax.help.search.MergingSearchEngine.merge(MergingSearchEngine.java:82)
at javax.help.JHelpSearchNavigator.merge(JHelpSearchNavigator.java:160)
at javax.help.JHelp.addHelpSet(JHelp.java:322)
at javax.help.JHelp.helpSetAdded(JHelp.java:288)
at javax.help.HelpSet.fireHelpSetAdded(HelpSet.java:344)
at javax.help.HelpSet.add(HelpSet.java:256)
at com.sun.management.viper.console.gui.help.VHelpViewer.consoleAction(VHelpViewer.java:138)
at com.sun.management.viper.console.VConsole.notifyListeners(VConsole.java:566)
at com.sun.management.viper.console.VConsole.consoleAction(VConsole.java:512)
at com.sun.management.viper.console.gui.VGUIConsole.consoleAction(VGUIConsole.java:566)
at com.sun.management.viperimpl.console.gui.SMCConsole.consoleAction(SMCConsole.java:292)
at com.sun.management.viperimpl.console.BaseConsoleManager.notifyListeners(BaseConsoleManager.java:370)
at com.sun.management.viperimpl.console.gui.GUIConsoleManager.loadOnlineHelpForTool(GUIConsoleManager.java:1198)
at com.sun.management.viperimpl.console.BaseConsoleManager.loadToolAndReplaceStub(BaseConsoleManager.java:2139)
at com.sun.management.viperimpl.console.BaseConsoleManager$ClickLoader.run(BaseConsoleManager.java:2060)
at com.sun.management.viper.util.ThreadPool$ThreadWorker.run(ThreadPool.java:138)
Caused by: java.security.InvalidParameterException
at com.sun.java.help.search.DefaultSearchEngine.<init>(DefaultSearchEngine.java:75)
... 21 more
Can anyone tell me anything what is problem?
I am newby to solaris and any ideas will be appreaciated.
Thanks in advance
David Suladze

Try search the WEB for your display adapter drivers. However, most of new especially intergated graphics are still not supported.
You may try to get it working with xsun, run kdmconfig and specify as display adapter VGA or Super VGA. I know that in some cases it helps.
As well do the same with Xorg and run /usr/X11/bin/xorgcfg, try to find somekind of generic VGA in drivers that are listed there.
As I know, smc runs only in graphical mode.
I saved the settings and pressed F2 for testing. I could see the displayDid you see buttons on that display (something like "yes", "no")?
xsun is very hard to set with most of display adapters and monitors, sometimes it shows only part of the screen, so you might not to see these buttons. However if you see them, press "yes" (or something like that, I dont exactly remember). Then reboot and your computer should start the GUI.

Error in looking up the JMS Connection Factory

          Hi,
          I am using weblogic6.1. I created a JMS Connection factory from administrator
          console with the name QueueConnectionFactory..But when i restart the server and
          try to look up that factory its giving an NameNotFoundException...This is the
          entry of the factory in config.xml
          <JMSConnectionFactory JNDIName="QueueConnectionFactory"
          Name="QueueConnectionFactory" Targets="myserver"/>
          But if i change reapply the target server to myserver from admin console whenever
          restart the server it works fine..
          I dont know where is the problem..Can u please update me on the problem if u people
          have any idea.
          The trace of the exceptions i got is as below:
          java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to
          resolve QueueConnectionFactory. Resolved
          : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
          java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to resolve
          QueueConnectionFactory. Resolved: '' Unr
          esolved:'QueueConnectionFactory' ; remaining name ''
          Thanx
          Regards,
          Narayan


          Hi Zach,
          No, I dont think ur interpretation is right..Once the entry corresponding
          to JMS Connection Factory is there in config.xml, the server should automatically
          bind it at the time of booting.. right. Why should this administrator server come
          into the picture.
          Thanx
          "Zach" <[email protected]> wrote:
          >Don't know. Sounds like the admin server is not notifying JMS of the
          >changes under certain situations. You might post in the management.console
          >newsgroup.
          >
          >_sjz.
          >
          >"Narayan" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >> I am using weblogic6.1. I created a JMS Connection factory from
          >administrator
          >> console with the name QueueConnectionFactory..But when i restart the
          >server and
          >> try to look up that factory its giving an NameNotFoundException...This
          >is
          >the
          >> entry of the factory in config.xml
          >>
          >> <JMSConnectionFactory JNDIName="QueueConnectionFactory"
          >> Name="QueueConnectionFactory" Targets="myserver"/>
          >> But if i change reapply the target server to myserver from admin console
          >whenever
          >> restart the server it works fine..
          >> I dont know where is the problem..Can u please update me on the problem
          >if
          >u people
          >> have any idea.
          >> The trace of the exceptions i got is as below:
          >> ****************
          >> java.rmi.RemoteException: javax.naming.NameNotFoundException:
          >Unable to
          >> resolve QueueConnectionFactory. Resolved
          >> : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
          >> java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable
          >to
          >resolve
          >> QueueConnectionFactory. Resolved: '' Unr
          >> esolved:'QueueConnectionFactory' ; remaining name ''
          >>
          >> **********************
          >>
          >> Thanx
          >> Regards,
          >> Narayan
          >>
          >>
          >
          >

How to access local connection factory created within Foreign Server in OSB

Hi All
I am facing an issue in my config plan. We have a RIB Foreign server with the following local connection factory:
jms/RibAqJmsXATopicConnectionFactory
I am using the below in my configuration plan:
<cus:envValueAssignments>
<xt:envValueType>Service URI</xt:envValueType>
<xt:location xsi:nil="true"/>
<xt:owner>
<xt:type>ProxyService</xt:type>
<xt:path>RLTPReturnToWarehouse/ProxyServices/ConsumeRIBRTWMessages</xt:path>
</xt:owner>
<xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">jms://localhost:7001/jms.RibAqJmsXATopicConnectionFactory/jms.etASNInFromRIBToWH1</xt:value>
</cus:envValueAssignments>
and i am getting the below error:
[java]
[java] Loading customization File ./dev/OSBCustomizationFile.xml
[java] Customization applied to the created resources only []
[java] com.bea.wli.config.customization.EnvValueCustomization@553c13
[java] Unexpected error: com.bea.wli.sb.transports.TransportException
[java] Problem invoking WLST - Traceback (innermost last):
[java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 200, in ?
[java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 122, in importToALSBDomain
[java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
what am i missing here?

[java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
Looks like the JNDI that you created for the ConnectionFactory is not reflected in the server.
Login to WLS Console> Summary of Servers > server_name > View JNDI Tree
Browse to the JNDI tree and see if your JNDI is visible there. If it is not then, please restart the server and recheck.
Once you are able to find it in the JNDI tree, then execute the customization file.
If you have modified the existing JNDI properties (that have a small exclamatory symbol) then any changes to those are not reflected till all the servers in the cluster are restarted.
If it still does not work, then recreate a new Connection with a different name and then retry. It should work then.
Thanks,
Patrick

Error saving JCA Connection factory in PI NWA

Hi All,
I am facing an issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
error details : CF_XD1_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration failed, reason: "Can not set authentication user store "null" in security context "CF_XD1_180" for connector "CF_XD1_180" in application "sap.com/tc~sapjra".".
at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.addComponent(ConnectorContainerImpl.java:1005
i posted this in SAP PI forum also...
Error saving connection factory
Regards
ashutosh r

Hello Carme,
From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
This beautiful blog by William will surely help you rectify the problem.
/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
Kindly check if you have done the following in your configuration:
1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15"
2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
I hope this should solve your problem.
Regards, Gaurav.

Error saving connection factory

I was trying to create a JCA connection factory so that I can use the user module to convert IDOCs to flat file. But I was encountering this problem when saving
Saving JCA Connection Factory: CF_ID1_800 failed due to: Can not add connection factory
I use NWA_SUPERADMIN role.. But seems like even that can't save it correctly.
THanks

Hi Brian,
I am also facing the same issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
could you share info, how your issue got solved..
Regards
ashutosh r

Rsh disconnect problems in Solaris 10

My company uses rsh to transmit data to proprietary cards, from Ultra 25's running Solaris 10. We're experiencing random timeouts. The error is rsh connection timeout.
We never had this problem on Solaris 8 or Solaris 7.
Has anyone run across this before? It's to random to run snoop on. Thanks Mark

type passwd mgcusr as root. then you'll need to type new password for that user.

How to annotate connection factory name in MDB?

How do I annotate connection factory name in Message Driven Bean?
@MessageDriven(ejbName = "MyMessageDrivenBean",
    destinationJndiName = "MyMessageDrivenBeanJndiName",
    destinationType = "javax.jms.Queue")
//I want to annotate the below in MDB
<connection-factory-jndi-name>local-jndi-name-of-queue-connection-factory</connection-factory-jndi-name>

I think the problem is in the activation config properties
@MessageDriven(name = "MyMessageDrivenBean", activationConfig = {
          @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
          @ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/MyQueue") })
public class MyMDB implements MessageListener
take a look at http://download.oracle.com/javaee/5/api/javax/ejb/ActivationConfigProperty.html

Can't deploy a jms connection factory

I am getting errors when trying to deploy a jms connection factory. Here is the xml file jms-factories.xml:
<?xml version="1.0" encoding="utf-8"?>
<jms-factories>
<application-name>MyApplicationName</application-name>
<connection-factory>
<connection-factory-type>QueueConnectionFactory</connection-factory-type >
     <factory-name>MyQueueConnectionFactory</factory-name>
<context-factory-type>
<link-factory-name>jmsfactory/default/MyConnectionFactory</link-factory-name>
<initial-context-factory>
      com.sap.engine.services.jndi.InitialContextFactoryImpl
</initial-context-factory>
<provider-url>localhost</provider-url>
<security-principal>Administrator</security-principal>
</context-factory-type>
</connection-factory>
</jms-factories>
Below is the error:
java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 5215450:com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Class loading error: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of MyConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:650)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:638)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.loadFactory(JmsContainerImpl.java:1306)
     at com.sap.engine.services.jmsconnector.container.JmsContainerImpl.prepareStart(JmsContainerImpl.java:577)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:233)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:193)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:421)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:539)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:171)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:315)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3163)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:674)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:658)
     at com.sap.engine.services.jmsconnector.container.JmsManagerImpl.deployJmsResource(JmsManagerImpl.java:281)
     at com.sap.engine.services.jmsconnector.command.DeployJmsResource.exec(DeployJmsResource.java:81)
     at com.sap.engine.services.shell.processor.environment.CommandBase.exec(CommandBase.java:132)
     at com.sap.engine.services.shell.processor.Interpreter.applyLineCommand(Interpreter.java:391)
     at com.sap.engine.services.shell.processor.Interpreter.apply(Interpreter.java:150)
     at com.sap.engine.services.shell.processor.Shell.work(Shell.java:148)
I am actually trying to do an automated deploy but I kept getting this error so I am trying to manually deploy it with the J2EE Engine Console tool. The command is:
deploy_jms_resource d:\jay\jms-factories.xml
Anybody have any ideas? At the top of the stack trace it mentions Class loading error but it is not the InitialContextFactoryImpl that is causing the problem because if I enter a totally bogus class name I get a nice ClassNotFound exception.

Hi Jay,
Which Reference guide do you mean? You find the jms-resources.xsd here: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/55e7d51e-0e01-0010-7b84-a95ee55eadeb">Java Messaging</a>, pages 52-58.

OJMS Connection Factory Error

Hi,
(Platforms: OC4J developer preview 4, JDev 10.1.3 EA, Database :Oracle 10.1.0 )
I have tried to implement the JMS provider (OJMS) according to the following document :
http://www.oracle.com/technology/sample_code/tech/java/codesnippet/jms/datasources/ResourceProvider.html
In my client code while I try to get the queue by :
queue = (Queue)jndiContext.lookup("java:comp/resource/TestRP/Queues/RPQueue");
there is no problem. But when I try to get connection factory by :
queueConnectionFactory = (QueueConnectionFactory) jndiContext.lookup("java:comp/resource/TestRP/QueueConnectionFactories/RPTable");
it fails and gives the following exception:
05/11/28 11:40:19 javax.naming.NamingException: Lookup error: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910; nested exception is:
     java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910 [Root exception is java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910]
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:68)
05/11/28 11:40:19      at javax.naming.InitialContext.lookup(InitialContext.java:351)
05/11/28 11:40:19      at BServlet.insertToQueue(BServlet.java:224)
05/11/28 11:40:19      at BServlet.doPost(BServlet.java:199)
05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
05/11/28 11:40:19      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:846)
05/11/28 11:40:19      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:397)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
05/11/28 11:40:19      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:245)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:231)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler.access$1000(ServerSocketAcceptHandler.java:33)
05/11/28 11:40:19      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:820)
05/11/28 11:40:19      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
05/11/28 11:40:19      at java.lang.Thread.run(Thread.java:595)
05/11/28 11:40:19 Caused by: java.io.InvalidClassException: oracle.oc4j.sql.ManagedDataSource; local class incompatible: stream classdesc serialVersionUID = 317676162977152905, local class serialVersionUID = 3384326427122904910
05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:100)
05/11/28 11:40:19      at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:83)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:341)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:158)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:235)
05/11/28 11:40:19      at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:55)
05/11/28 11:40:19      ... 18 more
Any idea?
Thanks,

Hi Brian,
I am also facing the same issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file.            we are on SAP PI 7.11 sp06....
error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
could you share info, how your issue got solved..
Regards
ashutosh r

Connection factory creation problem on Solaris

Similar Messages

Maybe you are looking for