Target namespacce uri
I was just trying to create a simple webservice using the Workshop. All that the
webservice will do is to take firstname and last name as input and conctenate
them in the output. But, when I try to build the webservice it says
ERROR: Tushar.jws:24:Bad schema-element annotation value.
ERROR: SUGGESTION: The current schema type system does not contain an element
'XML' in target namespace ''.
XML is the root tag of my XML and I did not specify the target-namespace URI.
I tried specifying some URI but that created more problems. What URI do I need
to provide for the target namespace.
In my sample XML I have chosen not to use any prefix for the namespace at all.
Is that mandatory?
Tushar,
Could you please attach your JWS file?
Also, let me know if you have changed any properties from the Properties
pallette for the JWS as a whole or for specific methods in the JWS?
Regards,
Anurag
"Tushar" <[email protected]> wrote in message
news:3f1a196a$[email protected]..
>
I was just trying to create a simple webservice using the Workshop. Allthat the
webservice will do is to take firstname and last name as input andconctenate
them in the output. But, when I try to build the webservice it says
ERROR: Tushar.jws:24:Bad schema-element annotation value.
ERROR: SUGGESTION: The current schema type system does not contain anelement
'XML' in target namespace ''.
XML is the root tag of my XML and I did not specify the target-namespaceURI.
I tried specifying some URI but that created more problems. What URI do Ineed
to provide for the target namespace.
In my sample XML I have chosen not to use any prefix for the namespace atall.
Is that mandatory?
Similar Messages
-
I get this exception (and long stack trace) when attempting to start my weblogic server. I'm running Weblogic 7 with Portal 7 (sp 1). I'm using Oracle 8.1.7. I upgraded this application from weblogic portal 4.0, and never had this problem there. As part of the migration process, I ran the tool to migrate all of the database tables, and I re-synched the EBCC project using version 7 of EBCC. I did a search for this problem and found a few mentions of it that seemed to be related to Oracle's handling of CLOB data. Apparently, there is a patch, but I can't seem to find this patch. I'm also not sure if this is indeed the problem since I didn't have this issue with the older version of weblogic using the same database. Any suggestions?
If you have a support contract please open a case so we can work through
this problem.
Can you run an sqlplus session on your database, execute the commands
"delete from data_sync_item" and "commit", then resync to see if it will
get you around the problem. The data_sync_item table will be fully
populated after you sync. This should get you running.
Between 4.0 and 7.0 the DefaultRequestPropertySet.req file was reduced
in size -- the CLOB would be smaller in the data_sync_item table.
I would recommend using the Version Checker against your installation --
find it on the dev2dev.bea.com site to see if the upgrade installer work
ed properly. Also consider running the full installer to avoid possible
problems that might occur with upgrade installers.
As a result of that patch you referenced in 4.0 the CLOB handling logic
was changed in 7.0 -- this is why it is strange you are seeing cleaving
errors. In 7.0 SP2 to be release next week the data sync and
persistence code was changed also.
Are you using the OCI or Thin driver?
-- Jim
Rob Goldie wrote:
Jim Litton <replyto@newsgroup> wrote:
Rob,
The CLOB issue was related to wlportal4.0 and should not be a factor
in
7.0.
Could you post the entire stack trace?
####<Jan 27, 2003 4:21:47 PM EST> <Warning> <Data Synchronization> <PFIDEV5> <pfeAricept1Server>
<main> <kernel identity> <> <000000> <Application: gmiAriceptApp; Failed to retrieve
a schema URI (document namespace) for /request/DefaultRequestPropertySet.req;
please see the following exception for details.>
Exception[com.bea.p13n.management.data.doc.DocumentProcessingException: Unable
to analyze and/or cleave document]
at com.bea.p13n.management.data.doc.cleaver.CleavingDocumentProcessor.process(CleavingDocumentProcessor.java:94)
at com.bea.p13n.management.data.repository.internal.DataItemImpl.getSchemaUri(DataItemImpl.java:136)
at com.bea.p13n.management.data.repository.DataRepositoryFactory.createDataItem(DataRepositoryFactory.java:363)
at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.createDataItems(JdbcDataSource.java:523)
at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:442)
at com.bea.p13n.management.data.repository.persistence.ReadOnlyJdbcPersistenceManager.refresh(ReadOnlyJdbcPersistenceManager.java:107)
at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:193)
at com.bea.p13n.management.data.repository.internal.MasterDataRepository.<init>(MasterDataRepository.java:46)
at com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataRepository(DataRepositoryFactory.java:255)
at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl.ejbCreate(PlaceholderServiceImpl.java:191)
at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl_9p0jz2_Impl.ejbCreate(PlaceholderServiceImpl_9p0jz2_Impl.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:151)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:864)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:81)
at weblogic.j2ee.Application.addComponent(Application.java:294)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:164)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:417)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:926)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
at $Proxy9.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:4060)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:2259)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:373)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
Caused by: org.xml.sax.SAXException: No message available. Resource not found:
repository.cleaver.no.xsi.namespace.exception Resource bundle: com/bea/p13n/management/data/datasync
at com.bea.p13n.management.data.doc.cleaver.DocumentCleaver.mapNamespaces(DocumentCleaver.java:135)
at com.bea.p13n.management.data.doc.cleaver.DocumentCleaver.startElement(DocumentCleaver.java:235)
at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1384)
at weblogic.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1299)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1821)
at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:964)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:396)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1119)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:133)
at com.bea.p13n.management.data.doc.cleaver.CleavingDocumentProcessor.process(CleavingDocumentProcessor.java:80)
at com.bea.p13n.management.data.repository.internal.DataItemImpl.getSchemaUri(DataItemImpl.java:136)
at com.bea.p13n.management.data.repository.DataRepositoryFactory.createDataItem(DataRepositoryFactory.java:363)
at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.createDataItems(JdbcDataSource.java:523)
at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:442)
at com.bea.p13n.management.data.repository.persistence.ReadOnlyJdbcPersistenceManager.refresh(ReadOnlyJdbcPersistenceManager.java:107)
at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:193)
at com.bea.p13n.management.data.repository.internal.MasterDataRepository.<init>(MasterDataRepository.java:46)
at com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataRepository(DataRepositoryFactory.java:255)
at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl.ejbCreate(PlaceholderServiceImpl.java:191)
at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl_9p0jz2_Impl.ejbCreate(PlaceholderServiceImpl_9p0jz2_Impl.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:151)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:864)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:81)
at weblogic.j2ee.Application.addComponent(Application.java:294)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:164)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:417)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:926)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
at $Proxy9.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:4060)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:2259)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:373)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
Are you using a UTF-8 Oracle database?
Yes
If you create a new User Profile in the EBCC and compare it to your
migrated .usr file do you see differences in the DTD's?
I recreated a new version of the .usr in the EBCC, and still got the same error.
I also tried deleting everything from the data-sync-item table and re-synching.
What does the DocumentManager section of your application-config.xml
look like?
<DocumentManager
ContentCacheName="documentContentCache"
ContentCaching="true"
DocumentConnectionPoolName="default"
MaxCachedContentSize="32768"
MetadataCacheName="documentMetadataCache"
MetadataCaching="true"
Name="default"
PropertyCase="none"
UserIdInCacheKey="false"
/>
What does the document.jar Targets="" parameter look like in config.xml?
<EJBComponent Name="document" Targets="pfeCluster" URI="document.jar"/>
-- Jim
Rob Goldie wrote:
I get this exception (and long stack trace) when attempting to start
my weblogic server. I'm running Weblogic 7 with Portal 7 (sp 1). I'm
using Oracle 8.1.7. I upgraded this application from weblogic portal
4.0, and never had this problem there. As part of the migration process,
I ran the tool to migrate all of the database tables, and I re-synched
the EBCC project using version 7 of EBCC. I did a search for this problem
and found a few mentions of it that seemed to be related to Oracle's
handling
of CLOB data. Apparently, there is a patch, but I can't seem to find
this patch. I'm also not sure if this is indeed the problem since I
didn't have this issue with the older version of weblogic using the
same database. Any suggestions? -
Can't install thunar: perl-uri issue?
trying to install thunar, i get these errors:
root@homer:/home/sero # pacman -S thunar
:: exo-devel conflicts with exo-dev. Remove exo-dev? [Y/n]
Remove: exo-dev
Targets: perl-uri-1.35-1 exo-devel-0.3.1.10rc1-2 thunar-0.4.0rc1-1
Total Package Size: 1.7 MB
Proceed with upgrade? [Y/n]
:: Retrieving packages from extra...
perl-uri-1.35-1 [################] 100% 75K 73.1K/s 00:00:01
:: Retrieving packages from community...
exo-devel-0.3.1.10rc1-2 [################] 100% 635K 313.0K/s 00:00:02
thunar-0.4.0rc1-1 [################] 100% 1010K 314.3K/s 00:00:03
checking package integrity... done.
removing exo-dev... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
perl-uri: /usr/lib/perl5/site_perl/current/URI.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/Escape.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/Heuristic.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/QueryParam.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/Split.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/URL.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/WithBase.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_foreign.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_generic.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_ldap.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_login.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_query.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_segment.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_server.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/_userpass.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/data.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file/Base.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file/FAT.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file/Mac.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file/OS2.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file/QNX.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file/Unix.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/file/Win32.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/ftp.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/gopher.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/http.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/https.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/ldap.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/ldapi.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/ldaps.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/mailto.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/mms.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/news.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/nntp.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/pop.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/rlogin.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/rsync.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/rtsp.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/rtspu.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/sip.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/sips.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/snews.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/ssh.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/telnet.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/tn3270.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/urn.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/urn/isbn.pm: exists in filesystem
perl-uri: /usr/lib/perl5/site_perl/current/URI/urn/oid.pm: exists in filesystem
errors occurred, no packages were upgraded.
should i just delete those .pm files and try again? :?:i just moved URI to URI.sus (my standard thing for "suspend"), and URI.pm to URI.pm.sus, and it installed and seems to work. good to know i can just delete the old ones. i was not sure what package or perl program they might be associated with. thx
>>> edit:
root@homer:/usr/lib/perl5/site_perl/current/URI.sus # pacman -Qo *
No package owns Escape.pm
No package owns Heuristic.pm
No package owns QueryParam.pm
No package owns Split.pm
No package owns URL.pm
No package owns WithBase.pm
No package owns _foreign.pm
No package owns _generic.pm
No package owns _ldap.pm
No package owns _login.pm
No package owns _query.pm
No package owns _segment.pm
No package owns _server.pm
No package owns _userpass.pm
No package owns data.pm
No package owns file
No package owns file.pm
No package owns ftp.pm
No package owns gopher.pm
No package owns http.pm
No package owns https.pm
No package owns ldap.pm
No package owns ldapi.pm
No package owns ldaps.pm
No package owns mailto.pm
No package owns mms.pm
No package owns news.pm
No package owns nntp.pm
No package owns pop.pm
No package owns rlogin.pm
No package owns rsync.pm
No package owns rtsp.pm
No package owns rtspu.pm
No package owns sip.pm
No package owns sips.pm
No package owns snews.pm
No package owns ssh.pm
No package owns telnet.pm
No package owns tn3270.pm
No package owns urn
No package owns urn.pm
hmm, the paranoid part of me starts whispering: maybe you were hacked and someone installed some perl thing at some point? :shock: -
Urgent ---StagedTargets, Targets, cluster
Hi everyone,
please help me.
Till now I did not have cluster in my project. I had only one weblogic server
running in my domain and it is server1.
Now I want to make a cluster of 2 servers say server1 and server2 where server2
will be running one special ejb component say spejb.jar. All other ejbs will be
deployed on server1.
As per my knowledge, the stagedTargets indicate the servers having latest version
of the application and in this case I want to mention server1 because i will be
keeping all the latest versions in server1. Does the following piece of config.xml
work correctly in this scenario ?
<Application Deployed="true" Name="ejb/SPEJB"
Path="./config/domain/applications/ejb" StagedTargets="server1">
<EJBComponent Name="ejb/SPEJB" Targets="server1" URI="spejb.jar"/>
</Application>
I guess, targets should be server2 and that is the only change i will have to
do ?
If I mention target="server1", I guess there is no point in having server2.
Since I want to run spejb.jar only on server2, I guess I do not have to mention
clustername as the targets.
I would highly appreciate if anyone can guide me in this matter.
thanks
Hi all
Anybody has met the same problem? Do you have any advises? Thank you very much! -
Topic consumer does not show up in destination after WLS restart
Hello JMS cracks
<p>We have following setup: <br>
- 1 Admin and 2 Managed WLS 8.1 SP4 on same host:<br>
- distributed topic destination<br>
- external jms topic subscriber client (using weblogic.jar)
</p>
<p>
The client subscribes to the topic in the following way:
<p>
TopicConnectionFactory fact = (TopicConnectionFactory) ctx.lookup("factName");<br>
TopicConnection tcon = fact.createTopicConnection();<br>
tcon.setExceptionListener(exceptionListener); <br>
TopicSession tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);<br>
Topic topic = (Topic) ctx.lookup("logicNameOfDistributedTopic");<br>
TopicSubscriber treceiver = tsession.createSubscriber(topic,selector,false);<br>
treceiver.setMessageListener(messageListener);
</p>
<p>
Test scenario: <br>
- start admin WLS and both managed WLS with URLs t3://host1:27100 and t3://host1:27200, respectively<br>
<br>
- start client with URL t3://host1:27100<br>
=> client receives messages :-)<br>
<br>
- kill client and start client again with URL t3://host1:27200<br>
=> client receives messages :-)<br>
<br>
- kill client and start client again with URL t3://host1:27100,host1:27200<br>
=> client receives messages :-)<br>
<br>
- kill WLS instance, e.g. t3://host1:27100<br>
=> Two possibilies: <br>
1) the client was connected to t3://host1:27100 and it has not to reconnect; it still receives messages :-) (however, an internal tester told me, that it also may stop receiving messages :-(<br>
<br>
2) client receives an Exception and reconnects to t3://host1:27200 (exceptionListener). It <b>may or may not receive messages</b> :-( <br>
<br>
- start WLS instance t3://host1:27100 again<br>
- kill client which is connected to t3://host1:27200 and start client with URL t3://host1:27100<br>
=> client connects to t3://host1:27100, but it <b>may or may not receive messages</b> :-( <br>
<br>
- kill client which is connected to t3://host1:27100 and start client with URL t3://host1:27200<br>
=> client connects to t3://host1:27200, but it <b>may or may not receive messages</b> :-( <br>
</p>
<p>
Going to the Weblogic console <myClusterDomain> > JMS Servers> <my JMS Server on t3://host1:27200> Active JMS Destinations one can see that the topic subscriber may or may not be added to the consumer count. If it is not added, the client does not receive any messages and vice versa.
</p>
<p>
This is very very annoying.
</p>
<p>
Please, can somebody tell me what can lead to this behaviour? Is something wrong with the configuration (if yes which parameter have I to adjust)? Is this just a timeing problem? Is there a workaround? Or is this normal (I hope not)?
</p>
<p>
Thanks very much for your help.
</p>
<p>
Peter
</p>Please find below the relevant parts of our config.xml.
Thanks for your help, Peter
<?xml version="1.0" encoding="UTF-8"?>
<Domain ConfigurationVersion="8.1.4.0" Name="devtClusterDomain">
<Cluster ClusterAddress="zueux32.sma.ch:27100,zueux32.sma.ch:27200"
MulticastAddress="237.0.0.1" MulticastPort="27900" Name="devtCluster"/>
<Server AcceptBacklog="50" Cluster="" DefaultProtocol="t3"
DefaultSecureProtocol="t3s" ExpectedToRun="false"
HttpdEnabled="true" ListenAddress="zueux32.sma.ch"
ListenPort="27000" Machine="zueux32" Name="devtAdmin"
NativeIOEnabled="true" ReliableDeliveryPolicy="RMDefaultPolicy"
ServerVersion="8.1.4.0" StdoutDebugEnabled="false"
StdoutSeverityLevel="32" TransactionLogFilePrefix="./logs/"
TunnelingClientPingSecs="45" TunnelingClientTimeoutSecs="40">
<WebServer AuthCookieEnabled="true"
LogFileName="./logs/access.log" LoggingEnabled="true" Name="devtAdmin"/>
<COM Name="devtAdmin"/>
<ServerStart
Arguments="-Dlog4j.configuration=file:/opt/bea/weblogic81/common/lib/workshopLogCfg.xml"
BeaHome="/opt/bea/weblogic81"
ClassPath="/opt/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/opt/bea/weblogic81/common/lib/log4j.jar:/opt/bea/weblogic81/server/lib/debugging.jar:/opt/bea/weblogic81/server/lib/knex.jar:/opt/bea/weblogic81/javelin/lib/javelin.jar:/opt/bea/weblogic81/server/lib/wlw-lang.jar:/opt/bea/jdk142_05/lib/tools.jar:/opt/bea/weblogic81/server/lib/weblogic_sp.jar:/opt/bea/weblogic81/server/lib/weblogic.jar:/opt/bea/weblogic81/server/lib/ant/ant.jar:/opt/bea/jdk142_05/jre/lib/rt.jar::/opt/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/bea/weblogic81/server/lib/webserviceclient.jar:/opt/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/opt/bea/weblogic81/server/lib/xbean.jar:/opt/bea/weblogic81/server/lib/wlxbean.jar:/opt/bea/weblogic81/server/lib/xqrl.jar:/opt/bea/weblogic81/server/lib/netui/netui-compiler.jar:/opt/bea/weblogic81/server/lib/wli.jar:/opt/bea/weblogic81/server/lib/fop.jar:/opt/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar"
JavaHome="/opt/bea/jkd142_05" Name="devtAdmin"
RootDirectory="/var/bea/domains/devtClusterDomain" SecurityPolicyFile="/opt/bea/weblogic81/server/lib/weblogic.policy"/>
<SSL Enabled="false" IdentityAndTrustLocations="KeyStores" Name="devtAdmin"/>
<Log FileMinSize="20000" Name="devtAdmin" RotationType="bySize"/>
<KernelDebug Name="devtAdmin"/>
<KernelDebug Name="devtAdmin"/>
<ServerDebug Name="devtAdmin"/>
<ExecuteQueue Name="weblogic.kernel.Default"/>
<JTAMigratableTarget Name="devtAdmin" UserPreferredServer="devtAdmin"/>
</Server>
<Server Cluster="devtCluster" ExpectedToRun="true"
GracefulShutdownTimeout="30" ListenAddress="zueux32.sma.ch"
ListenPort="27100" MSIFileReplicationEnabled="true"
Machine="zueux32" Name="devtMan1" NativeIOEnabled="true" ServerVersion="8.1.4.0">
<SSL Enabled="false" IdentityAndTrustLocations="KeyStores" Name="devtMan1"/>
<ExecuteQueue Name="weblogic.kernel.Default"/>
<ServerStart
Arguments="-Dlog4j.configuration=file:/opt/bea/weblogic81/common/lib/workshopLogCfg.xml"
BeaHome="/opt/bea/weblogic81"
ClassPath="/opt/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/opt/bea/weblogic81/common/lib/log4j.jar:/opt/bea/weblogic81/server/lib/debugging.jar:/opt/bea/weblogic81/server/lib/knex.jar:/opt/bea/weblogic81/javelin/lib/javelin.jar:/opt/bea/weblogic81/server/lib/wlw-lang.jar:/opt/bea/jdk142_05/lib/tools.jar:/opt/bea/weblogic81/server/lib/weblogic_sp.jar:/opt/bea/weblogic81/server/lib/weblogic.jar:/opt/bea/weblogic81/server/lib/ant/ant.jar:/opt/bea/jdk142_05/jre/lib/rt.jar::/opt/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/bea/weblogic81/server/lib/webserviceclient.jar:/opt/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/opt/bea/weblogic81/server/lib/xbean.jar:/opt/bea/weblogic81/server/lib/wlxbean.jar:/opt/bea/weblogic81/server/lib/xqrl.jar:/opt/bea/weblogic81/server/lib/netui/netui-compiler.jar:/opt/bea/weblogic81/server/lib/wli.jar:/opt/bea/weblogic81/server/lib/fop.jar:/opt/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar"
JavaHome="/opt/bea/jkd142_05" Name="devtMan1"
OutputFile="/var/bea/domains/devtClusterDomain/./NodeManagerClientLogs/devtClusterDomain_devtMan1/startServer_12_07_2006-16_42_57-4.log"
PasswordEncrypted="{3DES}wgEfvC0PoLDAO9eJ0RGXBg=="
RootDirectory="/var/bea/domains/devtClusterDomain"
SecurityPolicyFile="/opt/bea/weblogic81/server/lib/weblogic.policy" Username="weblogic"/>
</Server>
<Server Cluster="devtCluster" ExpectedToRun="true"
GracefulShutdownTimeout="30" ListenAddress="zueux32.sma.ch"
ListenPort="27200" MSIFileReplicationEnabled="true"
Machine="zueux32" Name="devtMan2" NativeIOEnabled="true" ServerVersion="8.1.4.0">
<SSL Enabled="false" IdentityAndTrustLocations="KeyStores" Name="devtMan2"/>
<ExecuteQueue Name="weblogic.kernel.Default"/>
<ServerStart
Arguments="-Dlog4j.configuration=file:/opt/bea/weblogic81/common/lib/workshopLogCfg.xml"
BeaHome="/opt/bea/weblogic81"
ClassPath="/opt/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/opt/bea/weblogic81/common/lib/log4j.jar:/opt/bea/weblogic81/server/lib/debugging.jar:/opt/bea/weblogic81/server/lib/knex.jar:/opt/bea/weblogic81/javelin/lib/javelin.jar:/opt/bea/weblogic81/server/lib/wlw-lang.jar:/opt/bea/jdk142_05/lib/tools.jar:/opt/bea/weblogic81/server/lib/weblogic_sp.jar:/opt/bea/weblogic81/server/lib/weblogic.jar:/opt/bea/weblogic81/server/lib/ant/ant.jar:/opt/bea/jdk142_05/jre/lib/rt.jar::/opt/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/bea/weblogic81/server/lib/webserviceclient.jar:/opt/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/opt/bea/weblogic81/server/lib/xbean.jar:/opt/bea/weblogic81/server/lib/wlxbean.jar:/opt/bea/weblogic81/server/lib/xqrl.jar:/opt/bea/weblogic81/server/lib/netui/netui-compiler.jar:/opt/bea/weblogic81/server/lib/wli.jar:/opt/bea/weblogic81/server/lib/fop.jar:/opt/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar"
JavaHome="/opt/bea/jkd142_05" Name="devtMan2"
OutputFile="/var/bea/domains/devtClusterDomain/./NodeManagerClientLogs/devtClusterDomain_devtMan2/startServer_12_13_2006-14_29_44-4.log"
PasswordEncrypted="{3DES}wgEfvC0PoLDAO9eJ0RGXBg=="
RootDirectory="/var/bea/domains/devtClusterDomain"
SecurityPolicyFile="/opt/bea/weblogic81/server/lib/weblogic.policy" Username="weblogic"/>
</Server>
<MigratableTarget Cluster="devtCluster" Name="devtMan1 (migratable)"
Notes="This is a system generated default migratable target for a server. Do not delete manually." UserPreferredServer="devtMan1"/>
<MigratableTarget Cluster="devtCluster" Name="devtMan2 (migratable)"
Notes="This is a system generated default migratable target for a server. Do not delete manually." UserPreferredServer="devtMan2"/>
<UnixMachine Name="zueux32" PostBindGID="gs-weblogic"
PostBindGIDEnabled="true" PostBindUID="weblogic" PostBindUIDEnabled="true">
<NodeManager ListenAddress="localhost" Name="zueux32"/>
</UnixMachine>
<ApplicationManager Name="devtClusterDomain"/>
<Application Deployed="true" LoadOrder="1000"
Name="JWSQueueTransport" Path="/opt/bea/weblogic81/server/lib"
StagedTargets="devtMan1,devtMan2" TwoPhase="true">
<EJBComponent Name="QueueTransportEJB" Targets="devtCluster" URI="QueueTransportEJB.jar"/>
</Application>
<SNMPAgent Name="devtClusterDomain"/>
<Log FileMinSize="20000" FileName="./wl-domain.log"
Name="devtClusterDomain" RotationType="bySize"/>
<JMSConnectionFactory
JNDIName="weblogic.jws.jms.QueueConnectionFactory"
Name="cgQueue"
Notes="User transactions must be enabled to ensure transaction coordination for persistence and asynchronous operations"
Targets="devtCluster" UserTransactionsEnabled="true"/>
<JMSDistributedQueue JNDIName="jws.queue"
Name="dist_cgJWSQueue_auto" Targets="devtCluster">
<JMSDistributedQueueMember JMSQueue="cgJWSQueue_auto_1" Name="cgJWSQueue_auto_1_OF_cgJMSServer_auto_1"/>
<JMSDistributedQueueMember JMSQueue="cgJWSQueue_auto_2" Name="cgJWSQueue_auto_2_OF_cgJMSServer_auto_2"/>
</JMSDistributedQueue>
<JMSFileStore Directory="rmfilestore" Name="FileStore"/>
<JMSJDBCStore ConnectionPool="cgJMSPool-nonXA"
Name="cgJMSStore_auto_1" PrefixName="dev_1"/>
<JMSJDBCStore ConnectionPool="cgJMSPool-nonXA"
Name="cgJMSStore_auto_2" PrefixName="dev_2"/>
<JMSServer Name="cgJMSServer_auto_1" Store="cgJMSStore_auto_1" Targets="devtMan1 (migratable)">
<JMSQueue JNDIName="jws.queue_auto_1" Name="cgJWSQueue_auto_1"
RedeliveryLimit="2" StoreEnabled="default"/>
</JMSServer>
<JMSServer Name="cgJMSServer_auto_2" Store="cgJMSStore_auto_2" Targets="devtMan2 (migratable)">
<JMSQueue JNDIName="jws.queue_auto_2" Name="cgJWSQueue_auto_2"
RedeliveryLimit="2" StoreEnabled="default"/>
</JMSServer>
<WSReliableDeliveryPolicy DefaultRetryCount="10"
DefaultTimeToLive="60000" Name="RMDefaultPolicy" Store="FileStore"/>
<JMSServer Name="WSStoreForwardInternalJMSServerdevtAdmin"
Store="FileStore" Targets="devtAdmin">
<JMSQueue CreationTime="1137587420880"
JNDIName="jms.internal.queue.WSStoreForwardQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSStoreForwardQueuedevtAdmin"/>
<JMSQueue CreationTime="1137587421219"
JNDIName="jms.internal.queue.WSDupsEliminationHistoryQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSDupsEliminationHistoryQueuedevtAdmin"/>
</JMSServer>
<JDBCConnectionPool ConnectionCreationRetryFrequencySeconds="30"
ConnectionReserveTimeoutSeconds="30"
DriverName="weblogic.jdbc.oracle.OracleDriver"
InactiveConnectionTimeoutSeconds="30" InitialCapacity="3"
MaxCapacity="10" Name="DataDispatcher Connection Pool"
PasswordEncrypted="{3DES}JLyzhkaCG14="
Properties="user=datdisp;SID=DWHDEVT"
ShrinkFrequencySeconds="60" StatementCacheSize="50"
Targets="devtMan1,devtMan2" TestConnectionsOnReserve="true"
TestFrequencySeconds="240"
TestTableName="SQL SELECT * FROM V_DB_STATUS" URL="jdbc:bea:oracle://zueux33:1521"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="jdbc/datadispatcher" Name="DataDispatcher Data Source"
PoolName="DataDispatcher Connection Pool" Targets="devtCluster"/>
<JMSTemplate DeliveryModeOverride="Persistent"
ExpirationPolicy="Log" MessagesMaximum="1000"
Name="Default JMS Template" RedeliveryDelayOverride="1000" RedeliveryLimit="20"/>
<JMSFileStore
Directory="/var/bea/domains/devtClusterDomain/filestores/devtMan1/ddreceiver" Name="Receiver File Store Man1"/>
<JMSFileStore
Directory="/var/bea/domains/devtClusterDomain/filestores/devtMan2/ddreceiver" Name="Receiver File Store Man2"/>
<JMSFileStore
Directory="/var/bea/domains/devtClusterDomain/filestores/devtMan1/ddsender" Name="Sender File Store Man1"/>
<JMSFileStore
Directory="/var/bea/domains/devtClusterDomain/filestores/devtMan2/ddsender" Name="Sender File Store Man2"/>
<JMSServer Name="Receiver JMS-Server Man1"
Store="Receiver File Store Man1" Targets="devtMan1 (migratable)" TemporaryTemplate="Default JMS Template">
<JMSQueue CreationTime="1137593696886"
JNDIName="jms/dataDispatcher.receiver@Receiver JMS-Server Man1"
Name="DataDispatcher Receiver Distributed Queue@Receiver JMS-Server Man1" Template="DataDispatcher Receiver Distributed Queue"/>
</JMSServer>
<JMSServer Name="Receiver JMS-Server Man2"
Store="Receiver File Store Man2" Targets="devtMan2 (migratable)" TemporaryTemplate="Default JMS Template">
<JMSQueue CreationTime="1137593696919"
JNDIName="jms/dataDispatcher.receiver@Receiver JMS-Server Man2"
Name="DataDispatcher Receiver Distributed Queue@Receiver JMS-Server Man2" Template="DataDispatcher Receiver Distributed Queue"/>
</JMSServer>
<JMSServer Name="Sender JMS-Server Man1"
Store="Sender File Store Man1" Targets="devtMan1 (migratable)" TemporaryTemplate="Default JMS Template">
<JMSQueue CreationTime="1137593759170"
JNDIName="jms/dataDispatcher.sender@Sender JMS-Server Man1"
Name="DataDispatcher Sender Distributed Queue@Sender JMS-Server Man1" Template="DataDispatcher Sender Distributed Queue"/>
<JMSQueue CreationTime="1137593828640"
JNDIName="jms/dataDispatcher.jmsHandlerQueue@Sender JMS-Server Man1"
Name="JMSHandler Distributed Queue@Sender JMS-Server Man1" Template="JMSHandler Distributed Queue"/>
<JMSTopic CreationTime="1138625625006"
DeliveryModeOverride="Persistent"
JNDIName="jms/dataDispatcher.jmsHandlerTopic@Sender JMS-Server Man1"
Name="JMSHandler Distributed Topic@Sender JMS-Server Man1" Template="JMSHandler Distributed Topic"/>
</JMSServer>
<JMSServer Name="Sender JMS-Server Man2"
Store="Sender File Store Man2" Targets="devtMan2 (migratable)" TemporaryTemplate="Default JMS Template">
<JMSQueue CreationTime="1137593759133"
JNDIName="jms/dataDispatcher.sender@Sender JMS-Server Man2"
Name="DataDispatcher Sender Distributed Queue@Sender JMS-Server Man2" Template="DataDispatcher Sender Distributed Queue"/>
<JMSQueue CreationTime="1137593828610"
JNDIName="jms/dataDispatcher.jmsHandlerQueue@Sender JMS-Server Man2"
Name="JMSHandler Distributed Queue@Sender JMS-Server Man2" Template="JMSHandler Distributed Queue"/>
<JMSTopic CreationTime="1138625624566"
DeliveryModeOverride="Persistent"
JNDIName="jms/dataDispatcher.jmsHandlerTopic@Sender JMS-Server Man2"
Name="JMSHandler Distributed Topic@Sender JMS-Server Man2" Template="JMSHandler Distributed Topic"/>
</JMSServer>
<JMSTemplate DeliveryModeOverride="Persistent"
ExpirationPolicy="Log"
Name="DataDispatcher Receiver Distributed Queue"
RedeliveryDelayOverride="1000" RedeliveryLimit="20"/>
<JMSDistributedQueue JNDIName="jms/dataDispatcher.receiver"
Name="DataDispatcher Receiver Distributed Queue"
Targets="devtCluster" Template="DataDispatcher Receiver Distributed Queue">
<JMSDistributedQueueMember
JMSQueue="DataDispatcher Receiver Distributed Queue@Receiver JMS-Server Man1" Name="DataDispatcher Receiver Distributed Queue@Receiver JMS-Server Man1"/>
<JMSDistributedQueueMember
JMSQueue="DataDispatcher Receiver Distributed Queue@Receiver JMS-Server Man2" Name="DataDispatcher Receiver Distributed Queue@Receiver JMS-Server Man2"/>
</JMSDistributedQueue>
<JMSTemplate DeliveryModeOverride="Persistent"
ExpirationPolicy="Log"
Name="DataDispatcher Sender Distributed Queue"
RedeliveryDelayOverride="1000" RedeliveryLimit="20"/>
<JMSDistributedQueue JNDIName="jms/dataDispatcher.sender"
Name="DataDispatcher Sender Distributed Queue"
Targets="devtCluster" Template="DataDispatcher Sender Distributed Queue">
<JMSDistributedQueueMember
JMSQueue="DataDispatcher Sender Distributed Queue@Sender JMS-Server Man2" Name="DataDispatcher Sender Distributed Queue@Sender JMS-Server Man2"/>
<JMSDistributedQueueMember
JMSQueue="DataDispatcher Sender Distributed Queue@Sender JMS-Server Man1" Name="DataDispatcher Sender Distributed Queue@Sender JMS-Server Man1"/>
</JMSDistributedQueue>
<JMSTemplate ExpirationPolicy="Log"
Name="JMSHandler Distributed Queue"
RedeliveryDelayOverride="1000" RedeliveryLimit="20"/>
<JMSDistributedQueue ForwardDelay="60"
JNDIName="jms/dataDispatcher.jmsHandlerQueue"
Name="JMSHandler Distributed Queue" Targets="devtCluster" Template="JMSHandler Distributed Queue">
<JMSDistributedQueueMember
JMSQueue="JMSHandler Distributed Queue@Sender JMS-Server Man2" Name="JMSHandler Distributed Queue@Sender JMS-Server Man2"/>
<JMSDistributedQueueMember
JMSQueue="JMSHandler Distributed Queue@Sender JMS-Server Man1" Name="JMSHandler Distributed Queue@Sender JMS-Server Man1"/>
</JMSDistributedQueue>
<JMSTemplate DeliveryModeOverride="Persistent"
ExpirationPolicy="Log" Name="JMSHandler Distributed Topic"
RedeliveryDelayOverride="1000" RedeliveryLimit="20" TimeToLiveOverride="-1"/>
<JMSDistributedTopic JNDIName="jms/dataDispatcher.jmsHandlerTopic"
Name="JMSHandler Distributed Topic" Targets="devtCluster" Template="JMSHandler Distributed Topic">
<JMSDistributedTopicMember
JMSTopic="JMSHandler Distributed Topic@Sender JMS-Server Man2" Name="JMSHandler Distributed Topic@Sender JMS-Server Man2"/>
<JMSDistributedTopicMember
JMSTopic="JMSHandler Distributed Topic@Sender JMS-Server Man1" Name="JMSHandler Distributed Topic@Sender JMS-Server Man1"/>
</JMSDistributedTopic>
<Application Name="xplg" Path="/var/tmp"
StagedTargets="devtMan1,devtMan2,devtAdmin" StagingMode="stage" TwoPhase="true">
<WebAppComponent Name="xplg" Targets="devtCluster" URI="xplg"/>
</Application>
<JDBCConnectionPool DriverName="weblogic.jdbc.oracle.OracleDriver"
Name="methodenPool" PasswordEncrypted="{3DES}NIZOVDL+tBI="
Properties="user=meteoch;portNumber=1521;SID=dwhdevt;serverName=zueux33"
Targets="devtCluster" TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:bea:oracle://zueux33:1521"/>
<JDBCTxDataSource JNDIName="jdbc/methoden" Name="methodenDataSource"
PoolName="methodenPool" Targets="devtCluster"/>
<Application Name="ws_dwh_methodenSession"
Path="/var/tmp/scp/ws_dwh_methodenSession.ear"
StagedTargets="devtMan1,devtAdmin,devtMan2" StagingMode="stage" TwoPhase="true">
<WebServiceComponent Name="dwh_methodenSession"
Targets="devtCluster" URI="dwh_methodenSession.war"/>
<EJBComponent Name="MethodenWebServiceEJB.jar"
Targets="devtCluster" URI="MethodenWebServiceEJB.jar"/>
</Application>
<Server Cluster="c1" ExpectedToRun="true" ListenPort="1111"
Machine="zueux32" Name="m1" ServerVersion="8.1.4.0">
<ServerDebug Name="m1"/>
<SSL IdentityAndTrustLocations="KeyStores" Name="m1"/>
<KernelDebug Name="m1"/>
<Log Name="m1"/>
<ServerStart Name="m1"
OutputFile="/var/bea/domains/devtClusterDomain/./NodeManagerClientLogs/devtClusterDomain_m1/startServer_12_07_2006-11_16_05-110.log"
PasswordEncrypted="{3DES}wgEfvC0PoLDAO9eJ0RGXBg==" Username="weblogic"/>
<WebServer Name="m1"/>
<COM Name="m1"/>
<IIOP Name="m1"/>
<JTAMigratableTarget Name="m1" UserPreferredServer="m1"/>
<JTARecoveryService Name="m1"/>
</Server>
<Server Cluster="c1" ExpectedToRun="true" ListenPort="2222"
Machine="zueux32" Name="m2" ServerVersion="8.1.4.0">
<ServerDebug Name="m2"/>
<SSL IdentityAndTrustLocations="KeyStores" Name="m2"/>
<KernelDebug Name="m2"/>
<Log Name="m2"/>
<ServerStart Name="m2"
OutputFile="/var/bea/domains/devtClusterDomain/./NodeManagerClientLogs/devtClusterDomain_m2/startServer_12_07_2006-11_10_32-82.log"
PasswordEncrypted="{3DES}wgEfvC0PoLDAO9eJ0RGXBg==" Username="weblogic"/>
<WebServer Name="m2"/>
<COM Name="m2"/>
<IIOP Name="m2"/>
<JTAMigratableTarget Name="m2" UserPreferredServer="m2"/>
<JTARecoveryService Name="m2"/>
</Server>
<Cluster Name="c1"/>
<MigratableTarget Cluster="c1" Name="m1 (migratable)"
Notes="This is a system generated default migratable target for a server. Do not delete manually." UserPreferredServer="m1"/>
<MigratableTarget Cluster="c1" Name="m2 (migratable)"
Notes="This is a system generated default migratable target for a server. Do not delete manually." UserPreferredServer="m2"/>
<JMSServer Name="j1" Targets="m1 (migratable)">
<JMSTopic CreationTime="1165485063006" JNDIName="t1" Name="t1"/>
</JMSServer>
<JMSServer Name="j2" Targets="m2 (migratable)">
<JMSTopic CreationTime="1165485075834" JNDIName="t2" Name="t2"/>
</JMSServer>
<JMSTemplate Name="d1"/>
<JMSDistributedTopic JNDIName="d1" Name="d1" Targets="c1" Template="d1">
<JMSDistributedTopicMember JMSTopic="t1" Name="dt1"/>
<JMSDistributedTopicMember JMSTopic="t2" Name="dt2"/>
</JMSDistributedTopic>
<JMSConnectionFactory JNDIName="f1" Name="f1" Targets="c1"/>
<Application Name="DataDispatcher"
Path="/home/zue/users/kep/proj/datadispatcher/dist/DataDispatcher.ear"
StagingMode="nostage" TwoPhase="true">
<EJBComponent Name="DataDispatcherBeans.jar"
Targets="devtCluster" URI="DataDispatcherBeans.jar"/>
<WebAppComponent Name="DataDispatcherAdminWeb"
Targets="devtCluster" URI="DataDispatcherAdminWeb"/>
<WebAppComponent Name="ReceiverServlet" Targets="devtCluster" URI="ReceiverServlet"/>
<WebAppComponent Name="SenderServlet" Targets="devtCluster" URI="SenderServlet"/>
<WebAppComponent Name="datadispatcherui" Targets="devtCluster" URI="datadispatcherui"/>
</Application>
</Domain>
Edited by peter05 at 12/18/2006 11:59 PM -
Error while Deploying WebApp in exploded form on 6.1
Hi,
I am trying to deploy a webapp named "test" in the exploded form on 6.1 and the following is what I have put in the config.xml file. I am using SP2.
<Application Deployed="true" Name="test" Path=".\config\coolDomain\applications">
<WebAppComponent Name="test" Targets="myserver" URI="test>
</Application>
I receive the following error while bringing up the server :
<Feb 28, 2002 2:00:48 PM PST> <Error> <HTTP> <[test] Error reading Web applicatio
n ".\config\coolDomain\applications\test"
java.net.UnknownHostException: java.sun.com
Any help would be appreciated.
Thanks !Ok, I got it , My webapp now gets registered. Thanks !!!!
Lata Rao <[email protected]> wrote:
Hi,
I am using 6.1 with Service pack 2.But this did not as yet solve the
problem.
Also weblogic_sp.jar included in the classpath which I suppose is the
service pack jar is not available in the lib directory. Has the service
pack been incorporated in some other jar ?
Any insight into this will be appreciated.
Thanks much.
- Lata Rao. -
Error 404--Not Found while accessing web app through Weblogic 6.1
Hi everybody,
I am new to Weblogic and recently installed Weblogic6.1
on my machine and I am trying to access my application using weblogic
and it gives
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
I have uploaded the WAR file of my application using the Admin
console. The WAR file is place under
\bea\wlserver6.1\config\mydomain\applications\screen.war.
What am I doing wrong ?
Thanks is advance.
PS: I am also including my web.xml file
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<session-config>
<session-timeout>-1</session-timeout>
</session-config>
<!-- Action Servlet Configuration -->
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
<init-param>
<param-name>application</param-name>
<param-value>resources.nmr.ApplicationResources</param-value>
</init-param>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>validate</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<!-- Action Servlet Mapping -->
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<!-- PDF servlet configuration -->
<servlet>
<servlet-name>pdf</servlet-name>
<servlet-class>com.abbott.gprd.servlets.PdfServlet</servlet-class>
</servlet>
<!-- PDF servlet Mapping -->
<servlet-mapping>
<servlet-name>pdf</servlet-name>
<url-pattern>/pdf</url-pattern>
</servlet-mapping>
<!-- MIME Mapping -->
<mime-mapping>
<extension>mol</extension>
<mime-type>chemical/x-mdl-molfile</mime-type>
</mime-mapping>
<!-- The Welcome File List -->
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<!-- Application Tag Library Descriptor -->
<taglib>
<taglib-uri>/WEB-INF/app.tld</taglib-uri>
<taglib-location>/WEB-INF/app.tld</taglib-location>
</taglib>
<!-- Struts Tag Library Descriptors -->
<taglib>
<taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
<taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/nmr.tld</taglib-uri>
<taglib-location>/WEB-INF/nmr.tld</taglib-location>
</taglib>
</web-app>
hmm
it all looks ok to me
what happens if you try to access an image or something in your war (ie
something not java related)
also - i have seen on some machines that localhost doesnt work but 127.0.0.1
does work
your app should be trying to access index.jsp which should be in the root
directory of your war
does index.jsp exist and is it in the root directory of your war?
lastly - i noticed you have a startup servlet. Put a system.out in the init
method of the servlet. If the servlet is being deployed OK then you should
see some output in the console
"Ravi" <[email protected]> wrote in message
news:[email protected]...
> I am specifying the same http://localhost:7001/screen and it still
> gives the same error.
>
> Following is part of my cofig.xml where myapp is specified.
>
> <CustomRealm
>
ConfigurationData="user.filter=(&(cn=%u)(objectclass=person));user.dn=ou
=people,
> o=example.com;server.principal=cn=admin,
>
o=example.com;membership.filter=(&(member=%M)(objectclass=groupofuniquen
ames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.ho
st=ldapserver.example.com;server.ssl=true;group.dn=ou=groups,
> o=example.com"
> Name="defaultLDAPRealmForNovellDirectoryServices"
> Notes="This is provided as an example. Before enabling this
> Realm, you must edit the configuration parameters as appropriate for
> your environment."
> Password="{3DES}/4XkW5rmVvBHzFtI9SRK/g=="
> RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
> <Server ListenPort="7001" Name="myserver" NativeIOEnabled="true"
> TransactionLogFilePrefix="config/mydomain/logs/">
> <Log FileName="config/mydomain/logs/weblogic.log"
> Name="myserver"/>
> <SSL Enabled="true" ListenPort="7002" Name="myserver"
> ServerCertificateChainFileName="config/mydomain/ca.pem"
> ServerCertificateFileName="config/mydomain/democert.pem"
> ServerKeyFileName="config/mydomain/demokey.pem"/>
> <WebServer DefaultWebApp="DefaultWebApp"
> LogFileName="./config/mydomain/logs/access.log"
> LoggingEnabled="true" Name="myserver"/>
> <ServerDebug Name="myserver"/>
> <ExecuteQueue Name="default"/>
> <KernelDebug Name="myserver"/>
> <ServerStart Name="myserver"/>
> </Server>
> <Application Deployed="true" Name="screen"
> Path=".\config\mydomain\applications">
> <WebAppComponent Name="screen" Targets="myserver"
> URI="screen.war"/>
> </Application>
> <SNMPAgent Name="mydomain"/>
> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
> <ApplicationManager Name="mydomain"/>
> <JTA Name="mydomain"/>
>
> Thanks in advance.
> Ravi.
>
>
> "Matt Krevs" <[email protected]> wrote in message
news:<[email protected]>...
> > what url are you specifying?
> >
> > i would guess that http://localhost/screen-web would work. Hard to say
> > without also seeing your config.xml
> >
> > The critical item in config.xml is the value of URI in the
webappcomponent
> > element for your application
> >
> > eg if it was
> >
> > <WebAppComponent Name="myapp-web" Targets="myerver" URI="myapp-web"/>
> >
> > then the url you would call is http://localhost/myapp-web
> >
> > "Ravi" <[email protected]> wrote in message
> > news:[email protected]...
> > > Hi everybody,
> > > I am new to Weblogic and recently installed Weblogic6.1
> > > on my machine and I am trying to access my application using weblogic
> > > and it gives
> > >
> > > Error 404--Not Found
> > > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
> > > 10.4.5 404 Not Found
> > >
> > > I have uploaded the WAR file of my application using the Admin
> > > console. The WAR file is place under
> > > \bea\wlserver6.1\config\mydomain\applications\screen.war.
> > >
> > > What am I doing wrong ?
> > >
> > > Thanks is advance.
> > >
> > > PS: I am also including my web.xml file
> > >
> > > <?xml version="1.0" encoding="ISO-8859-1"?>
> > >
> > > <!DOCTYPE web-app
> > > PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
> > > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
> > >
> > > <web-app>
> > >
> > > <session-config>
> > > <session-timeout>-1</session-timeout>
> > > </session-config>
> > >
> > > <!-- Action Servlet Configuration -->
> > > <servlet>
> > > <servlet-name>action</servlet-name>
> > >
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
> > > <init-param>
> > > <param-name>application</param-name>
> > > <param-value>resources.nmr.ApplicationResources</param-value>
> > > </init-param>
> > > <init-param>
> > > <param-name>config</param-name>
> > > <param-value>/WEB-INF/struts-config.xml</param-value>
> > > </init-param>
> > > <init-param>
> > > <param-name>debug</param-name>
> > > <param-value>2</param-value>
> > > </init-param>
> > > <init-param>
> > > <param-name>detail</param-name>
> > > <param-value>2</param-value>
> > > </init-param>
> > > <init-param>
> > > <param-name>validate</param-name>
> > > <param-value>true</param-value>
> > > </init-param>
> > > <load-on-startup>2</load-on-startup>
> > >
> > > </servlet>
> > >
> > > <!-- Action Servlet Mapping -->
> > > <servlet-mapping>
> > > <servlet-name>action</servlet-name>
> > > <url-pattern>*.do</url-pattern>
> > > </servlet-mapping>
> > >
> > > <!-- PDF servlet configuration -->
> > > <servlet>
> > > <servlet-name>pdf</servlet-name>
> > >
<servlet-class>com.abbott.gprd.servlets.PdfServlet</servlet-class>
> > > </servlet>
> > >
> > >
> > > <!-- PDF servlet Mapping -->
> > > <servlet-mapping>
> > > <servlet-name>pdf</servlet-name>
> > > <url-pattern>/pdf</url-pattern>
> > > </servlet-mapping>
> > >
> > > <!-- MIME Mapping -->
> > > <mime-mapping>
> > > <extension>mol</extension>
> > > <mime-type>chemical/x-mdl-molfile</mime-type>
> > > </mime-mapping>
> > >
> > >
> > > <!-- The Welcome File List -->
> > > <welcome-file-list>
> > > <welcome-file>index.jsp</welcome-file>
> > > </welcome-file-list>
> > >
> > > <!-- Application Tag Library Descriptor -->
> > > <taglib>
> > > <taglib-uri>/WEB-INF/app.tld</taglib-uri>
> > > <taglib-location>/WEB-INF/app.tld</taglib-location>
> > > </taglib>
> > >
> > > <!-- Struts Tag Library Descriptors -->
> > > <taglib>
> > > <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
> > > <taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
> > > </taglib>
> > >
> > > <taglib>
> > > <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
> > > <taglib-location>/WEB-INF/struts-html.tld</taglib-location>
> > > </taglib>
> > >
> > > <taglib>
> > > <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
> > > <taglib-location>/WEB-INF/struts-logic.tld</taglib-location>
> > > </taglib>
> > >
> > > <taglib>
> > > <taglib-uri>/WEB-INF/nmr.tld</taglib-uri>
> > > <taglib-location>/WEB-INF/nmr.tld</taglib-location>
> > > </taglib>
> > >
> > > </web-app>
-
Mapping of Web App context root and the physical directory of the web app
I'm running Weblogic 7.0 on Windows2000.The physical directory of my web application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directory I have
my JSPS, static HTML and WEB-INF. I define the context path of this web app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be created manually
also), the following entry gets inserted in the server's config.xml ,-
<Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the container knows
that for any request for the web app with context path as 'testapp', it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. In the above
process, nowhere such mapping is specified. I expected something like Tomcat's
server.xml, where in docbase we clearly specify this mapping between the context
path and the physical directory. Please help.Let me give some more details and hopefully this will make things clearer.
Say you deploy /foo/bar/myweb.war and in myweb.war you configure a
context-root of /rob
During deployment, the server creates an ApplicationMBean with a path of
/foo/bar/. It then creates a WebAppComponent with a uri of myweb.war.
Next, deployment calls back on the web container and tells it to deploy
the WebAppComponent. The web container reads the myweb.war, parses
descriptors etc. The web container then updates its data structures to
register that myweb.war has a context path of /rob. (It has to figure
out all the other servlet mappings as well.)
When a request for /rob/foo comes in, the web container consults its
data structures to determine which webapp and servlet receives the
request. This is not a linear search of all webapps and servlets.
There's much better ways to do pattern matching.
Hope this clears things up. Let me know if you still have questions.
-- Rob
Arindam Chandra wrote:
Thanks for the answer. Still one thing is not clear. Whatever context path I declare
for my web app as the value of <context-root> element in the weblogic.xml (in
my example it's "/testapp"), it is no where mapped with the "URI" attribute (or
any other attribute, sub-element whatsoever in the <Application> element).
Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
So when a request of the form http://myweblogic.com:7001/testapp/... arrives at
the server, how does the server knows that it has to serve this request with files
from D:\WL8\weblogic81\TestDeploy\build\TestWebApp ? It should not be like the
web container iterates thru all the web application entries in config.xml and
tries to match with one context-root declaration. I repeat, I expected some mapping
similar to Tomcat's server.xml, where in the <docbase> element u clearly specify
the mapping between the context path and the physical directory
Rob Woollen <[email protected]> wrote:
Arindam Chandra wrote:
I'm running Weblogic 7.0 on Windows2000.The physical directory of myweb application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directoryI have
my JSPS, static HTML and WEB-INF. I define the context path of thisweb app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be createdmanually
also), the following entry gets inserted in the server's config.xml,-
<>So the server will look for your web application at the Application Path
(D:\WL8\weblogic81\TestDeploy\build|) + the web uri (TestWebApp). So
it
maps the context-root you've specified /testapp to that path.
It's a little clearer in the case where you had a full-fledged EAR.
Then you'r application path would map to the "root" of the EAR, and the
uris would point to the various modules (eg webapps.)
-- Rob
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the containerknows
that for any request for the web app with context path as 'testapp',it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. Inthe above
process, nowhere such mapping is specified. I expected something likeTomcat's
server.xml, where in docbase we clearly specify this mapping betweenthe context
path and the physical directory. Please help. -
How to view the changes immediately after a jsp is modified?
Hi All,
How can I modify a JSP and view the changes immediately
without packing a war and deploying again.
The JSP may reference a tag library.
And also, I don't want to register the compiled jsp class
as servlet class in web.xml because there are hundreds of
jsp files.
Then, how can I do this to save the development time.
Any suggestion is appreciated.
Thanks!!!
Kammau
Hi Kammau,
the next thing you should do is:
- create a standard EAR (jar, not "exploded"), with application.xml,
manifest entries, etc.
- try to deploy. If you can't deploy this way, you still have some
problems which have nothing to do with the jsp-reload-thing. Solve them
first. (You can ask us, of course)
- if it works, try to deploy the EAR "exploded" with "exploded" WAR in it.
- if that works, try the jsp-reload.
Good luck,
Philip
Kammau wrote:
> Hi All,
> I try to deploy my jars (local ejbs) and my jsps separately.
>
> I have tried two ways, but all fail.
> 1. I create a app directory under my server directory (same as DefaultWebApp),
> and put all the jars and the war (exploded) under the directory. Then I add the
> script in the config.xml likes:
> <Application Deployed="true" Name="myApp" Path=".\config\mydomain\applications\myApp">
> <EJBComponent Name="myJar1.jar" Targets="myserver" URI="myJar1.jar"/>
> <EJBComponent Name="myJar1.jar" Targets="myserver" URI="myJar2.jar"/>
> <WebAppComponent Name="war" Targets="myserver" URI="war"/>
> </Application>
>
> //myJar1.jar and myJar2.jar are my jars and I put all jsps under the war directory.
>
> Unfortunately, it fails.
> I found the weblogic tried to deploy the jars and war, but both of jars and war
> can not be deployed.
>
> 2. I put the jars into a ear and I also create the
> app directory under my server directory (same as DefaultWebApp), and put the
> war (exploded) under the directory. Then I add the script in the config.xml likes:
> <Application Deployed="true" Name="myApp" Path=".\config\mydomain\applications\myApp">
> <WebAppComponent Name="war" Targets="myserver" URI="war"/>
> </Application>
>
> Unfortunately, it fails.
> In this case, I can deploy the jars, but when the weblogic tried to deploy the
> wars, it can not find the jndi names of my jars.
-
Unable to see Deployed EJB's in console
I'm having problems seeing my deployed EJB's and servlets on the
console. I'm running WL6.1 SP1.
My ejbs and servlets are in one jar file. This jar file is in
d:/javelin/deployment directory and not in the
bea/wlserver6.0/config/investia/applications directory.
Anyone have any idea on how I can fix this?
Below is my config.xml file.
Thanks,
Ruben
<!--If your domain is active, please do not edit the config.xml
file. Any changes made to that file while the domain is active will
not have any effect on the domain's configuration and are likely to be
lost. If your domain is inactive, you may edit this file with an XML
editor. If you do so, please refer to the configuration DTD. In
general, we recommend that changes to your configuration file be made
through the Administration Console.-->
<Domain
Name="investia"
>
<ApplicationManager
Name="investia"
/>
<Application
Deployed="true"
Name="console"
Path="./config/investia/applications"
>
<WebAppComponent
Name="console"
Targets="javelin"
URI="console.war"
/>
</Application>
<Application
Deployed="true"
Name="certificate"
Path="./config/investia/applications"
>
<WebAppComponent
Name="certificate"
Targets="javelin"
URI="certificate.war"
/>
</Application>
<Security
GuestDisabled="false"
Name="investia"
PasswordPolicy="mypasswordpolicy"
Realm="myRealm"
/>
<Application
Name="javelin.jar"
Path="d:/javelin/deployment"
>
<EJBComponent
Name="javelin.jar"
Targets="javelin"
URI="javelin.jar"
/>
</Application>
<JTA
Name="investia"
/>
<JDBCConnectionPool
CapacityIncrement="1"
DriverName="oracle.jdbc.driver.OracleDriver"
InitialCapacity="1"
MaxCapacity="20"
Name="ejbPool"
Properties="user=javelin;password=javelin;dll=ocijdbc8;server=devo_brutus;protocol=oci8"
Targets="javelin"
URL="jdbc:oracle:oci8:"
/>
<Log
FileName="investia.log"
Name="investia"
/>
<Realm
FileRealm="myFileRealm"
Name="myRealm"
/>
<FileRealm
Name="myFileRealm"
/>
<PasswordPolicy
LockoutEnabled="false"
MinimumPasswordLength="8"
Name="mypasswordpolicy"
/>
<JMSServer
Name="JMSServer-0"
/>
<Application
Name="bob.jar"
Path="d:/javelin/deployment"
>
<EJBComponent
Name="bob.jar"
Targets="javelin"
URI="bob.jar"
/>
</Application>
<Application
Deployed="true"
Name="DefaultWebApp_javelin-1"
Path="./config/investia/applications"
>
<WebAppComponent
Name="DefaultWebApp_javelin"
Targets="javelin"
URI="DefaultWebApp_javelin"
/>
</Application>
<Server
HelpPageURL="/weblogic/javelin/public_html/docs51/adminhelp/"
HttpdEnabled="true"
IdlePeriodsUntilTimeout="65534"
JDBCLogFileName="jdbc.log"
JDBCLoggingEnabled="false"
Name="javelin"
NativeIOEnabled="true"
PeriodLength="6000000"
StdoutEnabled="true"
SystemPassword="password"
ThreadPoolSize="25"
ZACEnabled="true"
ListenPort="11199"
StdoutSeverityLevel="64"
>
<SSL
CertificateCacheSize="3"
Enabled="false"
ListenPort="7002"
Name="javelin"
ServerCertificateChainFileName="config/investia/ca.pem"
ServerCertificateFileName="config/investia/democert.pem"
ServerKeyFileName="config/investia/demokey.pem"
/>
<ServerDebug
Name="javelin"
/>
<KernelDebug
Name="javelin"
/>
<Log
FileMinSize="4096"
FileName="javelin.log"
Name="javelin"
/>
<WebServer
DefaultWebApp="DefaultWebApp_javelin"
HttpsKeepAliveSecs="120"
KeepAliveSecs="60"
LogFileName="access.log"
LoggingEnabled="false"
Name="javelin"
Targets="javelin"
/>
</Server>
</Domain>An added note: In looking into other similar posts, I see instructions to "trash the file: com.apple.finder.plist" in User Library/Preferences. I was going to try that, and reload my preferences, but I do not have that file.
-
Directory Structure ?s for an Exploded Web Application
We have an application that consists only of JSPs and Servlets, no
EJBs. I am researching whether or not it's worthwhile to start using
EJBs. We're also migrating from Weblogic 5 to 6.1. I've managed to
migrate our application fine and have it up and running on WLS 6.1.
I'm confused about the exploded directory structure, the
application.xml file, where to put the EJBs and whether or not I have
to jar them. Here's our current directory structure:
DefaultWebApp/ JSPs here
DefaultWebApp/WEB-INF web.xml and weblogic.xml here
DefaultWebApp/WEB-INF/classes Servlets and other classes here
DefaultWebApp/WEB-INF/lib do my un-jar-ed EJBs go here?
I've been reading a lot of BEA's documentation, particularly
‘Deploying an Exploded J2EE Application' and a ‘Web Application PDF',
and looking for relevant threads on the weblogic.developer.interest
groups. It looks like the application.xml should go in a new
DefaultWebApp/META-INF directory. But where do the EJBs go?
I also see some directory structures with another /web directory
that's confusing me.
Oh, I've also managed to compile and jar up a trial Stateless Session
EJB. Then I think I ‘auto-deployed' it into the /applications
directory, and Weblogic seems to recognize it. But when I tried to
reference it in a JSP, I got an error message ‘class x is public,
should be declared in a file named x.java'. I'm assuming this is
related to the application.xml, where I need to define the ejb
directory.
Thanks.To deploy your web app together with your EJBs, you need to create
an "EAR" structure. Both your webapp and your EJB jars will be within
this new structure, at the same level. You may jar up your EJBs, or you
may explode their structure, it's up to you.
The resulting structure should look something like below:
EnterpriseApp/ <-- new top level
EnterpriseApp/META-INF/
EnterpriseApp/META-INF/application.xml
EnterpriseApp/lib/ <-- shared libraries (if any)
EnterpriseApp/EJB/ <-- ejbs go here
EnterpriseApp/EJB/META-INF/ejb-jar.xml
EnterpriseApp/EJB/META-INF/weblogic-ejb-jar.xml
EnterpriseApp/EJB/com/your/ejb/classes/here
EnterpriseApp/WebApp/ <-- move your current app here
EnterpriseApp/WebApp/index.jsp <-- JSPs goes here
EnterpriseApp/WebApp/other.jsp
EnterpriseApp/WebApp/WEB-INF/web.xml
EnterpriseApp/WebApp/WEB-INF/weblogic.xml
EnterpriseApp/WebApp/WEB-INF/lib <-- ui libraries go here
EnterpriseApp/WebApp/WEB-INF/classes <-- servlets go here
The above structure is identical to the structure to an EAR file, only "exploded"
as actual files and directories instead of being "jarred" into a single EAR file.
Your application.xml in this case would specify something like:
<application>
<display-name>EnterpriseApp</display-name>
<description>My Enterprise Application</display-name>
<module>
<ejb>EJB</ejb>
</module>
<module>
<web>
<web-uri>WebApp</web-uri>
<context-root>/yourAppRoot</context-root>
</web>
</module>
</application>
And in config.xml you would have an entry similar to:
<Application Deployed="true" Name="EnterpriseApp"
Path=".\config\mydomain\applications\EnterpriseApp">
<WebAppComponent Name="ui" Targets="myserver" URI="WebApp"/>
<EJBComponent Name="ejb" Targets="myserver" URI="EJB"/>
</Application>
regards,
-Ade -
Configuring Business Operations in WLIntegrator 2.1 Studio
Hi,
I deployed a SessionBean and few CMPs in a deployable jar on WLI 2.1.I was able
to test the deployment through a java client.
Now, when i go to a workflow template in WLI Studio and select Configuration-->Business
Operations and click on add button, I`m getting following exception on server console:
Started WebLogic Integration - BPM Server version 2.1
WebLogic Integration BPM server does not support NULL.
***** ASSERTION FAILED *****[ Unable to load remote interface: java.lang.ClassNotFoundException:
amit.lal.cmp.ProductCmp ]
Make sure your EJB is configured in the same Application as the WLPI code
Any pointers to what may be the problem and how to solve it.
Thanks,
Amit LalHi,
check in your administration console/Deployments/EJB: the WLPI application
code is propably deployed into the WLPI_Application. I did not find another
way to tell my EJB to be deployed in the same application than editing the
config.xml (which is hopefully not the recommended way to do it).
In the config.xml should be a tag like:
<Application Deployed="true" Name="WLPI_Application" Path="lib">
insert your myEjb.jar like the following (the URI has to be relative to the
given path, in this case "lib"!):
<Application Deployed="true" Name="WLPI_Application" Path="lib"
[other WLPI applications]
<EJBComponent Name="myEjb" Targets="myserver"
URI="../../../src/toplink/tutorial/ejbtest/myEjb.jar"/>
</Application>
Regards,
Astrid
Amit Lal <[email protected]> schrieb in im Newsbeitrag:
3d04a6e8$[email protected]..
>
Hi,
I deployed a SessionBean and few CMPs in a deployable jar on WLI 2.1.Iwas able
to test the deployment through a java client.
Now, when i go to a workflow template in WLI Studio and selectConfiguration-->Business
Operations and click on add button, I`m getting following exception onserver console:
>
>
Started WebLogic Integration - BPM Server version 2.1
WebLogic Integration BPM server does not support NULL.
***** ASSERTION FAILED *****[ Unable to load remote interface:java.lang.ClassNotFoundException:
amit.lal.cmp.ProductCmp ]
Make sure your EJB is configured in the same Application as the WLPI code
Any pointers to what may be the problem and how to solve it.
Thanks,
Amit Lal -
Hi
I got the following error when starting weblogic 8.1 server:
####<Jul 14, 2004 5:24:15 PM PDT> <Notice> <Security> <sjcpc044> <myserver> <Thread-1> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Jul 14, 2004 5:24:15 PM PDT> <Notice> <WebLogicServer> <sjcpc044> <myserver> <Thread-1> <<WLS Kernel>> <> <BEA-000327> <Starting WebLogic Admin Server "myserver" for domain "cdrdomain">
####<Jul 14, 2004 5:24:20 PM PDT> <Error> <JMS> <sjcpc044> <myserver> <Thread-1> <<WLS Kernel>> <> <BEA-040371> <JMSServer "JMSServer-0" JMS Server Session Pool is inavlid and has not been started "CMSessionPool". Exception is "weblogic.jms.common.ConfigurationException: Listener class, com.carescience.jms.CMMsgListener, not found".
weblogic.jms.common.ConfigurationException: Listener class, com.carescience.jms.CMMsgListener, not found
at weblogic.jms.backend.BEServerSessionPool.setListener(Ljava.lang.String;)V(BEServerSessionPool.java:283)
at weblogic.jms.backend.BEServerSessionPool.initialize()V(BEServerSessionPool.java:220)
at weblogic.jms.backend.BEServerSessionPool.<init>(Ljava.lang.String;Lweblogic.jms.common.JMSID;Lweblogic.jms.backend.BackEnd;Lweblogic.management.configuration.JMSSessionPoolMBean;)V(BEServerSessionPool.java:178)
at weblogic.jms.backend.BackEnd.createServerSessionPools()V(BackEnd.java:792)
at weblogic.jms.backend.BackEnd.resume()V(BackEnd.java:1314)
at weblogic.jms.JMSService.addJMSServer(Lweblogic.management.configuration.JMSServerMBean;)V(JMSService.java:2241)
at weblogic.jms.JMSService.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)V(JMSService.java:2012)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Lweblogic.management.configuration.DeploymentMBean;)Z(DeploymentTarget.java:330)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Ljava.util.List;)V(DeploymentTarget.java:590)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments()V(DeploymentTarget.java:568)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments()V(DeploymentTarget.java:240)
at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Native Method)
at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:711)
at weblogic.management.internal.DynamicMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(DynamicMBeanImpl.java:690)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ConfigurationMBeanImpl.java:476)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljava.lang.Object;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:947)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(RemoteMBeanServerImpl.java:908)
at weblogic.management.internal.MBeanProxy.invoke(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:946)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(Ljava.lang.String;[Ljava.lang.Object;)Ljava.lang.Object;(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments()V(ServerMBean_Stub.java:7271)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments()V(SlaveDeployer.java:1210)
at weblogic.management.deploy.slave.SlaveDeployer.resume()V(SlaveDeployer.java:362)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume()V(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:359)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
Here is the how the ListenerClass is set up for JMSSessionPool in config.xml. The com.carescience.jms.CMMsgListener class file is in cia.ear deployed as application for this domain.
<JMSServer Name="JMSServer-0" Store="jmsq" Targets="myserver">
<JMSSessionPool
ConnectionFactory="com.carescience.jms.ConnectionFactory"
ListenerClass="com.carescience.jms.CMMsgListener"
Name="CMSessionPool" SessionsMaximum="3">
<JMSConnectionConsumer
Destination="com.carescience.jms.CMTopic" Name="CMConnectionConsumer"/>
</JMSSessionPool>
<JMSTopic DestinationKeys="MDSDESTKEY"
JNDIName="com.carescience.jms.CMTopic" Name="CMTopic"/>
</JMSServer>
<Application Name="_appsdir_cia_ear"
Path="C:\bea81\user_projects\domains\cdrdomain\applications\cia.ear"
StagedTargets="myserver" StagingMode="stage" TwoPhase="true">
<EJBComponent Name="ejb_exchange.jar" Targets="myserver" URI="ejb_exchange.jar"/>
<EJBComponent Name="heartbeat.jar" Targets="myserver" URI="heartbeat.jar"/>
<WebAppComponent Name="cia" Targets="myserver" URI="cia.war"/>
<WebAppComponent Name="axis" Targets="myserver" URI="axis.war"/>
</Application>
I know we can avoid to the error by adding the jar file containing this class to the class path. But is there any other way?
Best Regards,
Kelvin ZhengYou could double-check in the JMS newsgroup, but I'm pretty sure that a statically configured listener like this would have to be in the classpath.
If possible, I'd encourage you to consider using a MDB instead. That could be in your EAR file instead.
-- Rob -
Startup error Unable to Find DocumentConnectionPool : Need Help
Iam getting an error when iam starting up the server.
trace is :
weblogic.ejb20.WLDeploymentException: Unable to find DocumentConnectionPool 'def
ault' configuration MBeanjavax.ejb.CreateException: Unable to find DocumentConne
ctionPool 'default' configuration MBean
at com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl.ejb
Create(SPIFastDocumentManagerImpl.java:328)
at com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl_lw3
66m_Impl.ejbCreate(SPIFastDocumentManagerImpl_lw366m_Impl.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionP
ool.java:151)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManag
er.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:
1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:404)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer
.java:983)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:969)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:619)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:194)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManag
er.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:
1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:404)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer
.java:983)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:969)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:619)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
My application-config.xml has :
<DocumentConnectionPool
CapacityIncrement="1"
DriverName="com.bea.p13n.content.document.jdbc.Driver"
InitialCapacity="5"
MaxCapacity="5"
Name="default"
Properties="schemaXML=D:/myServer/dmsBase/doc-schemas;docBase=D:/myServer/dmsBase;jdbc.dataSource=weblogic.jdbc.pool.commercePool"
URL="jdbc:beasys:docmgmt:com.bea.p13n.content.document.ref.RefDocumentProvider"
/>
and my config.xml has:
<Application Deployed="true" Name="MyApp"
Path="D:\apps\MyApp"
StagedTargets="myServer" TwoPhase="true">
<ApplicationConfiguration Name="MyApp"
Targets="myServer" URI="META-INF/application-config.xml"/>
</Application>
So , it is targetted on my server and also the app-config has it defined.
Can anyone tell me where is the problem.?For ne one who is interested,
we figured what went wrong in our configuration.
We are using oracle as backend but driver for the datasource under consideration is given is the driver for reference cloudscape database. Once driver is changed to oracle's OCI driver problem got resolved
Good luck :-)
Manohar -
Error at startup Unable to find DocumentConnectionPool , Need Help urgently
Iam getting an error when iam starting up the server.
trace is :
weblogic.ejb20.WLDeploymentException: Unable to find DocumentConnectionPool 'def
ault' configuration MBeanjavax.ejb.CreateException: Unable to find DocumentConne
ctionPool 'default' configuration MBean
at com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl.ejb
Create(SPIFastDocumentManagerImpl.java:328)
at com.bea.p13n.content.document.internal.SPIFastDocumentManagerImpl_lw3
66m_Impl.ejbCreate(SPIFastDocumentManagerImpl_lw366m_Impl.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionP
ool.java:151)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManag
er.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:
1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:404)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer
.java:983)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:969)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:619)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:194)
at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManag
er.java:380)
at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:
1472)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:404)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer
.java:983)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:969)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:619)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
My application-config.xml has :
<DocumentConnectionPool
CapacityIncrement="1"
DriverName="com.bea.p13n.content.document.jdbc.Driver"
InitialCapacity="5"
MaxCapacity="5"
Name="default"
Properties="schemaXML=D:/myServer/dmsBase/doc-schemas;docBase=D:/myServer/dmsBase;jdbc.dataSource=weblogic.jdbc.pool.commercePool"
URL="jdbc:beasys:docmgmt:com.bea.p13n.content.document.ref.RefDocumentProvider"
/>
and my config.xml has:
<Application Deployed="true" Name="MyApp"
Path="D:\apps\MyApp"
StagedTargets="myServer" TwoPhase="true">
<ApplicationConfiguration Name="MyApp"
Targets="myServer" URI="META-INF/application-config.xml"/>
</Application>
So , it is targetted on my server and also the app-config has it defined.
Can anyone tell me where is the problem.?For ne one who is interested,
we figured what went wrong in our configuration.
We are using oracle as backend but driver for the datasource under consideration is given is the driver for reference cloudscape database. Once driver is changed to oracle's OCI driver problem got resolved
Good luck :-)
Manohar
Maybe you are looking for
-
How do I delete something in "Extra", something I didn't put in! (on my desktop). On my laptop the "PDF -download, by Nitro PDF software" doesn't figure and pdf files open normally and not seperatly in the mainframe of for example www.centrum-veurne.
-
Adobe photoshop elements stopped working on Mac Pro
in January 2014 adobe photoshop elements purchased at i-tunes store. Always worked properly. Now since about a week, I can not start the program. After startup, he asks to sign up with my Apple ID, when I do this it gives the error message: Your devi
-
Object Oriented Programming concepts
Hi Friends, I need your help to understand the Object Oriented Programming concepts. Please help me- Thanks, Fl4syed
-
Calling Stored Procedure w/JPublisher generated classes
Hi, We are trying to pass Oracle nested tables as input/output parameters to several of our stored procedures to support bulk binding operations in the database from our applications. We have some database defined types and stored procedures that use
-
I cannot get my contacts through to my car by bluetooth.....any suggestions?