Appserver 8 -JMS
Hi,
I'm trying to deploy an application but it doesn't start up properly. There is a queue destination resource - jms/liferay/MailQueue with property imqDestinationName=MailDestination and I have created the physical destination MailDestination.
My server.log has the follwoing errors:
[#|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter
|_ThreadID=10;|rardeployment.exception_on_invoke_setter|#]
This doesn't look too serious but it is the 1st error in the log on server startup.
The serious errors start with:
[#|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.naming
|_ThreadID=10;|NAM5003: CommunicationException in SerialContext lookup()
com.sun.enterprise.resource.PoolingException
then lots of stack trace.....
leading to:
Caused by: java.lang.IllegalArgumentException: MQ:Queue:Invalid Queue Name -
at com.sun.messaging.Queue.setName(Queue.java:65)
Can someone enlighten me as to what is going on?
I tried changing the property name from "imqDestinationName" to "Name" the application still isn't loading. I used the GUI to create the destination under the
Application Server
- Java Message Service
- Physical Destinations
Tab I clicked on new. I have set up a CacheQueue resource with identical properties except for Cache replacing the word Mail everywhere - this doesn't seem to be giving any trouble.
I'm not sure if full stack trace will be helpful or not, but here goes anyway:
[#|2004-07-14T13:12:36.318+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB Timer Service properties : min delivery interval = 7000
max redeliveries = 1
redelivery interval = 5000|#]
[#|2004-07-14T13:12:36.319+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-07-14T13:12:36.320+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-07-14T13:12:42.596+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Dynamic proxies ENABLED for Local EJBs in com_liferay_counter_ejb_CounterManager|#]
[#|2004-07-14T13:12:42.738+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|[**BaseContainer [2.0]**]: com_liferay_counter_ejb_CounterManager. Instantiated BaseContainer...|#]
[#|2004-07-14T13:12:42.862+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|[Pool-com_liferay_counter_ejb_CounterManager]: Added PoolResizeTimerTask...|#]
[#|2004-07-14T13:12:42.864+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|[MonitoringMediator] currentLevel: OFF|#]
[#|2004-07-14T13:12:42.867+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|[Basecontainer] Registered Method Monitors|#]
[#|2004-07-14T13:12:42.868+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|[SLSB Container] registered monitorable|#]
[#|2004-07-14T13:12:42.875+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|Dynamic proxies ENABLED for Local EJBs in com_liferay_cache_ejb_CacheManager|#]
[#|2004-07-14T13:12:44.072+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/opt/SUNWappserver/imq/bin].|#]
[#|2004-07-14T13:12:44.075+0100|FINE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb.mdb|_ThreadID=10;|reconnect-delay-in-seconds=60, reconnect-max-retries=60, reconnect-enabled=false|#]
[#|2004-07-14T13:12:44.391+0100|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|rardeployment.exception_on_invoke_setter|#]
[#|2004-07-14T13:12:44.394+0100|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.naming|_ThreadID=10;|NAM5003: CommunicationException in SerialContext lookup()
com.sun.enterprise.resource.PoolingException
at com.sun.enterprise.connectors.AdministeredObjectResource.createAdministeredObject(AdministeredObjectResource.java:143)
at com.sun.enterprise.naming.factory.AdministeredObjectFactory.getObjectInstance(AdministeredObjectFactory.java:67)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:130)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:355)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:1759)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:376)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:135)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:191)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)
at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:125)
at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:96)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:170)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:200)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.security.PrivilegedActionException: com.sun.enterprise.resource.PoolingException
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.AdministeredObjectResource.createAdministeredObject(AdministeredObjectResource.java:139)
... 22 more
Caused by: com.sun.enterprise.resource.PoolingException
at com.sun.enterprise.connectors.util.SetMethodAction.run(SetMethodAction.java:79)
... 24 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.connectors.util.SetMethodAction.run(SetMethodAction.java:66)
... 24 more
Caused by: java.lang.IllegalArgumentException: MQ:Queue:Invalid Queue Name -
at com.sun.messaging.Queue.setName(Queue.java:65)
... 29 more
|#]
Similar Messages
-
WLST, how do I suppress unwanted stack traces and make WLST less verbose?
Hi everyone,
I've just started out with WLST but have ended up somewhat confused. My script works as intended but is very verbose.
Suppose I want to log in:
try:
connect(user, "wrong_password", url)
except WLSTException, err:
print str(err)
print "Run with option \"-h\" for help"The password is wrong so I get something like this printed out by me:
{noformat}
Error occured while performing connect : User: wm714, failed to be authenticated. Use dumpStack() to view the full stacktrace
{noformat}
But I also get a totally unwanted Java stack trace (before my message):
{noformat}This Exception occurred at Fri May 21 15:49:01 CEST 2010.
javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: wm714, failed to be authenticated.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:42)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:677)
{noformat}
I don't want to confuse the user with all that! I found this:
http://objectmix.com/weblogic/529822-wlst-exception-handling-unwanted-stack-trace.html
Which discusses WLS.commandExceptionHandler.setSilent(1) I'm running on WLS 10.3.0.0 and can execute that statement but it has no effect. I didn't even know about the WLS-object and I can find no documentation on commandExceptionHandler.
On the matter of verbosity, is there any way to get rid of stuff like:
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)I avoid using the "interactive" commands like cd and use stuff like getMBean("domainRuntime:/ServerRuntimes/" + appServer.getName()
+ "/JMSRuntime/" + appServer.getName() + ".jms/JMSServers") but I still get the clutter printed out.
Thanks!Workaround:
wlstOut = tempfile.mktemp(suffix="_wlst.txt")
redirect(wlstOut, "false")
... do useful stuff
stopRedirect()
os.remove(wlstOut)I would have preffered to turn off the messages (yes I could try /dev/null) but this will do. A funny thing is that the stack trace I wrote about doesn't appear in the log file. Somehow "redirect" must have a nice side effect.
/Roger -
Difference between Sun Enterprise Systems and JCAPS
Hi,
Can somebody explain to me the differences between Sun ES and JCAPS? Is it true that JCAPS is buit on top of Sun ES? Also, does JCAPS refer to a single product or a collection of products? Which are the products needed for a developer to start off?
Thankshi *,
CAPS is based on ES komponents like appserver or JMS server.
CAPS is one product (one ide & environment) with many modules (connectivity , bpm .....)
many products best is to read the manuals http://docs.sun.com/app/docs/prod/sj.caps#hic
regards chris -
How to define a JMS queuen in AppServer? Firewall-Ports?
How do I define a JMS queue in Oracles AppServer (for usage in SoaSuite)?
Which ports do I have to open in firewall to get the JMS queue be accessible from other (remote) computers?
PeterHi Peter,
You can find all information you need on Oracle Application Server JMS in the documentation:
http://download-west.oracle.com/docs/cd/B25221_04/web.1013/b14427/jms.htm
Including the ports if I'm correct. There's some nice links to HOW-TO documents as well.
I'm not that well familiar with JMS myself, but if I'm not mistaken it should not matter where you define your queues or topics, since they should be looked up through JNDI anyway. But please someone correct me if I'm wrong.
HTH,
Bas -
Can you specify third party JMS Provider in Weblogic appserver configuration
Can you specify third party JMS Provider in Weblogic appserver configuration ???
Only place i know of is that you can specify third party JMS Provider in MDB configuraion.
DOES Weblogic has some kind of configuration files where you specify JMS Provider
info (Like you can do that in JBOSS)
You can also specify a third-party JMS provider using the Messaging Bridge,
which transfers messages from one queue or topic to another.
And in general, inside WLS you can use any JMS provider you wish anywhere
that you can also use WLS JMS. In an upcoming release, there will also be
some support to make foreign JMS providers a little easier to configure.
But why would you want to use another JMS provider anyway? ;-)
greg
"Neeru Munjal" <[email protected]> wrote in message
news:[email protected]..
>
> Can you specify third party JMS Provider in Weblogic appserver
configuration ???
>
> Only place i know of is that you can specify third party JMS Provider in
MDB configuraion.
> DOES Weblogic has some kind of configuration files where you specify JMS
Provider
> info (Like you can do that in JBOSS)
-
JMS destinations disappear from JNDI after appserv restart
I am using the PE 8.1 2005Q1 application server. I create a jms resource as jms/myQueue and I can see it using the JNDI browser.
However, after restarting the application server, my destinations still show up under JMS Destinations & Admin Object Resources, but disappear from the JNDI browser and are unavailable to clients!
Do I need to perform an addtional step in order to get the appserver to persist these jndi registrations? There appears to be a disconnect between JMS and JNDI. Any help is greatly appreciated.JMS has a ForeignJMSProvider config option to do this I believe. 9.0 will also support this more generally.
-
JMS-related sun-appserver-pe8.0.0_01 default server start failure
On Dell Dimension 2400 XP system, appserver startup always fails after trying for 60 seconds to verify if the JMS service startup succeeded. This condition started 10 July. What is JMS? Why does it fail? What to do? Rich
Hi
The Java Message Service (JMS) is a messaging standard that allows application components based on the Java 2 Platform, Enterprise Edition (J2EE) to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous.
JMS is bundled and installed with Application Server 8. JMS runs on a port 17676. If this port is occupied by any other process, the JMS will not start. Please check if this port is occupied by any other process or change the default JMS port in domain.xml (<Creator-root>/Appserver8/domains/creator/config/domain.xml)
Thanks
SG -
Trying to create a JMS Client in LifeCycle Module. Sun Appserver 8
I have created a Lifecycle module which initializes a set of JMX Beans. One of them is a JMX Client.
I have created a JMS Queue Connection factory according to the guidelines and associated a JNDI name jms/TrQueueConnectionFactory.
I have created a destination of type Queue with JNDI name jms/catalogQueue.
When the code is trying to make get the reference to the queue connection factory, I encounter the following exception
NamingException
javax.naming.CommunicationException: serial context communication ex [Root exception is com.sun.enterprise.resource.PoolingException]
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:328)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.i2.catalog.services.request.BRR.startJmsConnection(BRR.java:662)
at com.i2.catalog.services.request.BRR.startService(BRR.java:514)
at com.i2.catalog.base.ServiceMBeanSupport.start(ServiceMBeanSupport.java:387)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at com.i2.catalog.base.ServiceManager.start(ServiceManager.java:347)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at com.i2.catalog.boot.CatalogController.start(CatalogController.java:401)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at com.i2.catalog.boot.Bootstrap.start(Bootstrap.java:188)
at com.transora.im.startup.SunAppServerStartup.initialize(SunAppServerStartup.java:164)
at com.transora.im.startup.SunAppServerStartup.handleEvent(SunAppServerStartup.java:98)
at com.sun.appserv.server.ServerLifecycleModule.postEvent(ServerLifecycleModule.java:192)
at com.sun.appserv.server.ServerLifecycleModule.onStartup(ServerLifecycleModule.java:234)
at com.sun.appserv.server.LifecycleModuleService.onStartup(LifecycleModuleService.java:194)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.enterprise.resource.PoolingException
at com.sun.enterprise.connectors.AdministeredObjectResource.createAdministeredObject(AdministeredObjectResource.java:143)
at com.sun.enterprise.naming.factory.AdministeredObjectFactory.getObjectInstance(AdministeredObjectFactory.java:67)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:304)
... 39 more
Caused by: java.security.PrivilegedActionException: com.sun.enterprise.connectors.ConnectorRuntimeException
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.AdministeredObjectResource.createAdministeredObject(AdministeredObjectResource.java:139)
... 42 more
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException
at com.sun.enterprise.connectors.util.SetMethodAction.handleException(SetMethodAction.java:110)
at com.sun.enterprise.connectors.util.SetMethodAction.run(SetMethodAction.java:96)
... 44 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.connectors.util.SetMethodAction.run(SetMethodAction.java:69)
... 44 more
Caused by: java.lang.IllegalArgumentException: MQ:Queue:Invalid Queue Name -
at com.sun.messaging.Queue.setName(Queue.java:64)
... 49 more
It seems that there is a security issue. Is there any entry I need to have in the sever.policy to make it happen.
Note: I have defined jdbc datasource for oracle and the jmx services are able to access the datasource via JNDI lookup
Your help and direction is deeply appreciated.
Thanks in advance,
ChithsAs I know, the lifecycle module is just an external RMI client that has your lifecycle controled by container.
Please, correct me if I am wrong, but there is no way to access JMS or Datasource via external RMI clients. -
Example of Weblogic Appserver using XA Controlled Transaction to send messages to third party JMS
I am looking for Example of Weblogic Appserver using XA Controlled Transaction
to send messages to third party JMS Server.
I want to send messages to JMS and use Weblogic MDB to consume that message and
send it to some third party JMS in a XA Controlled transaction.
Sure. Right now, it involves a bit of JTA programming -- in our next
release, it should be easier, however.
Before sending a message, you have to:
-- Use the TxHelper class to get the current Transaction object.
-- Use the "getXAResource" method on the JMS provider's Session object to
get the XAResource object for the JMS Session you're using to send.
-- Call "enlistResource" on the Transaction object.
You MUST do this in every transaction where you use the JMS provider to send
a message.
You can find the documentation for the TxHelper class and other
WebLogic-specific classes here:
http://e-docs.bea.com/wls/docs70/javadocs/index.html
Look for the "weblogic.transaction" package.
You can find documentation for the Transaction class (which defines
enlistResource) and other classes here:
http://java.sun.com/products/jta/javadocs-1.0.1/index.html
You should also use the weblogic.transaction.TransactionManager class and
call "registerDynamicResource" once (and only once) in your application to
register the JMS providers XAResource with JTA. This makes JTA more
efficient, and it makes transaction recovery work properly.
If the JMS provider is MQ, then look at the whitepaper "Using JTA
transactions to envelope WLS JMS and IBM MQSeries" here:
http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
And finally, if you have more questions, the transaction people will be able
to help more. Post to "weblogic.developer.interest.transaction".
greg
"Neeru Munjal" <[email protected]> wrote in message
news:[email protected]...
>
> I am looking for Example of Weblogic Appserver using XA Controlled
Transaction
> to send messages to third party JMS Server.
> I want to send messages to JMS and use Weblogic MDB to consume that
message and
> send it to some third party JMS in a XA Controlled transaction.
>
-
Transaction Help ? JMS and db2 database without appserver
We have a Queue and db2 database.
need to read the message from queue and write it to the database in a standalone application without appserver. Now question is how to have a single transaction for both the jobs?
Please advice!!!If you want to receive a JMS message and write to a database in the same transaction, then it sounds as if you are asking for the ability to enlist both transactional resources within the same XA transaction and then perform a two-phase commit of the two resources. If you use an application server then this is easy to configure.
Even if you don't want to use an application server (or some other container offering similar services), you will still need a transaction manager, but will need to enlist the transactional resources yourself. Possible but not easy. If an application server is too heavyweight, then look for lighter-weight alternatives.
Nigel -
Problem to send a message with JMS
Hi
I'm doing some tests with the api JMS to know how works. I have got some problems. I have been looking for some information but i don't find so much. I have got too doubts.
I am usinng Netbeans 5.5 with Sun Java System Application Server Platform Edition 9.0_01 (build b14).
I am trying to do it with ejb. Because in the future the application can have got so many connection in the same time.
The server shows me the next errors.
Starting Sun Java System Application Server Platform Edition 9.0_01 (build b14) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.6.0_03] from [Sun Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
sgmt.service_initialized
DPL5400:Exception occurred : error in opening zip file.
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://t1:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
JTS5014: Recoverable JTS instance, serverId = [3700]
About to load the system app: MEjbApp
LDR5010: All ejb(s) of [MEjbApp] loaded successfully!
About to load the system app: __ejb_container_timer_app
EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]
LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat-ejb moduleName=Chat-ejb ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.EJBModuleLoader.load(EJBModuleLoader.java:158)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:206)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:198)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
Caused by: javax.naming.NameNotFoundException
at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
... 17 more
CORE5021: Application NOT loaded: [Chat-ejb]
WEB0302: Starting Sun-Java-System/Application-Server.
WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]
WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]
WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]
WEB0100: Loading web module [amserver] in virtual server [server] at [/amserver]
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context ''
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context ''
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context '/asadmin'
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server [server] at [/__JWSappclients]
Using MQ RA for Broker lifecycle control
JMS Service Connection URL is :mq://t1:7676/
MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...
EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome D:\Sun\AppServer\imq\bin\.. -varhome D:/sun/AppServer/domains/domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}
[07/nov/2007:18:35:03 CET]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.6.0_03 Sun Microsystems Inc. D:\sun\Java\jdk1.6.0_03\jre
[07/nov/2007:18:35:03 CET] IMQ_HOME=D:\sun\AppServer\imq
[07/nov/2007:18:35:03 CET] IMQ_VARHOME=D:\sun\AppServer\domains\domain1\imq
[07/nov/2007:18:35:03 CET] Windows XP 5.1 x86 t1 (1 cpu) pepepc
[07/nov/2007:18:35:03 CET] Java Heap Size: max=506816k, current=46944k
[07/nov/2007:18:35:03 CET] Arguments: -port 7676 -name imqbroker -imqhome D:\Sun\AppServer\imq\bin\.. -varhome D:/sun/AppServer/domains/domain1\imq -useRmiRegistry -rmiRegistryPort 8686
[07/nov/2007:18:35:04 CET] [B1060]: Loading persistent data...
[07/nov/2007:18:35:04 CET] Using built-in file-based persistent store: D:\sun\AppServer\domains\domain1\imq\instances\imqbroker\
[07/nov/2007:18:35:04 CET] [B1189]: Cluster Service feature is not available
[07/nov/2007:18:35:04 CET] [B1039]: Broker "imqbroker@t1:7676" ready.
MQJMSRA_EB1101: run:EMBEDDED broker started with code =0
MQJMSRA_RA1101: SJSMQ JMS ResourceAdaapter configuration=
raUID =null
brokerType =EMBEDDED
brokerInstanceName =imqbroker
brokerBindAddress =null
brokerPort =7676
brokerHomeDir =D:\Sun\AppServer\imq\bin\..
brokerVarDir =D:/sun/AppServer/domains/domain1\imq
brokerJavaDir =D:/sun/Java/jdk1.6.0_03
brokerArgs =null
brokerStartTimeout =60000
adminUsername =admin
adminPassFile =E:\tempWin\asmq21980.tmp
useJNDIRmiServiceURL =true
rmiRegistryPort =8686
startRmiRegistry =false
useSSLJMXConnector =true
brokerEnableHA =false
clusterId =null
brokerId =null
jmxServiceURL =null
dbType =null
dbProps ={}
dsProps ={}
ConnectionURL =
UserName =guest
ReconnectEnabled =true
ReconnectInterval =5000
ReconnectAttempts =3
AddressListBehavior =RANDOM
AddressListIterations =3
InAppClientContainer =false
InClusteredContainer =false
GroupName =null
MQJMSRA_RA1101: start:SJSMQ JMSRA Connection Factory Config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverrideJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=true, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfiguredClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imqJMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http://localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostName=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefaultPassword=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=guest, imqReconnectEnabled=false, imqConnectionFlowCount=100, imqAddressListBehavior=PRIORITY, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimestamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsumerTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueueBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddressList=localhost:7676, imqOverrideJMSHeadersToTemporaryDestinations=false}
MQJMSRA_RA1101: SJSMQ JMSRA Started
endpoint.determine.destinationtype
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat moduleName=Chat-ejb_jar ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:184)
at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:113)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:206)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:204)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
Caused by: javax.naming.NameNotFoundException
at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
... 18 more
Registering ad hoc servlet: WebPathPath: context root = "/Chat", path = "/Chat-app-client'
Java Web Start services started for application com.sun.enterprise.appclient.jws.ApplicationContentOrigin@aabc2d registration name=Chat
[email protected]56b4 registration name=Chat, context root=/Chat/Chat-app-client, module name=
, parent=Chat
CORE5021: Application NOT loaded: [Chat]
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
JBISE6013: JavaEEServiceEngine : Java EE Service Engine started successfully.
CORE5024: EJB module [Chat-ejb] unloaded successfully!
DeployedItemRef postDeregistration failed. Load Balancer Monitoring MBeans might be lying around if this application is being load balanced
BPEL service engine started
ADM1064:The upload file at [E:\tempWin\s1astempdomain1server-162970426\Chat-ejb.jar] exists and will be overwritten.
ADM1006:Uploading the file to:[E:\tempWin\s1astempdomain1server-162970426\Chat-ejb.jar]
deployed with moduleid = Chat-ejb
ADM1041:Sent the event to instance:[ModuleDeployEvent -- enable ejb/Chat-ejb]
endpoint.determine.destinationtype
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat-ejb moduleName=D__sun_AppServer_domains_domain1_applications_j2ee-modules_Chat-ejb ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.EJBModuleLoader.load(EJBModuleLoader.java:158)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:219)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:174)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:406)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleEnabled(StandAloneEJBModulesManager.java:500)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:960)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:941)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:448)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:160)
at com.sun.enterprise.admin.server.core.AdminNotificationHelper.sendNotification(AdminNotificationHelper.java:128)
at com.sun.enterprise.admin.server.core.ConfigInterceptor.postInvoke(ConfigInterceptor.java:109)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:97)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:56)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:142)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:109)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.naming.NameNotFoundException
at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
... 54 more
CORE5020: Error while loading ejb module
{code}
I know it is very large. I think the error it is in this line.
{code}
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
{code}
also I am going to put the code.
file PublicarBean.java
{code}
package org.pepes;
import com.sun.tools.ws.processor.model.java.JavaArrayType;
import javax.annotation.Resource;
import javax.ejb.SessionContext;
import javax.ejb.Stateless;
import javax.jms.ConnectionFactory;
import javax.jms.QueueConnectionFactory;
import javax.jms.Topic;
import javax.naming.NamingException;
* @author pepes
@Stateless(mappedName="ejb/publicar")
public class publicarBean implements org.pepes.publicarRemote {
/** Creates a new instance of publicarBean */
@Resource(name="jms/QueueConnectionFactory")
private QueueConnectionFactory connectionFactory;
@Resource(name="jms/Topic", mappedName="jndi/Topic")
private Topic topic;
private javax.naming.InitialContext ctx;
public publicarBean() {
public void creaMensaje() throws javax.naming.NamingException , javax.jms.JMSException {
try {
javax.naming.InitialContext ctx = new javax.naming.InitialContext();
this.connectionFactory = (javax.jms.QueueConnectionFactory)ctx.lookup("jms/QueueConnectionFactory");
this.topic = (javax.jms.Topic)ctx.lookup("jms/Topic");
javax.jms.Connection connection = this.connectionFactory.createConnection();
javax.jms.TopicSession ts = (javax.jms.TopicSession)connection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE);
javax.jms.TopicPublisher tp = ts.createPublisher(this.topic);
javax.jms.TextMessage msg = ts.createTextMessage();
for (int i = 0; i<3;i++) {
msg.setText("Prueba: " + i);
tp.publish(msg);
catch (javax.jms.JMSException jmex) {
throw jmex;
{code}
the file publicarRemote.java
{code}
package org.pepes;
import javax.ejb.Remote;
* This is the business interface for publicar enterprise bean.
@Remote
public interface publicarRemote {
public void creaMensaje() throws javax.naming.NamingException , javax.jms.JMSException;
{code}
file mensaje.java
{code}
package org.pepes;
import javax.annotation.Resource;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.Message;
import javax.jms.MessageListener;
* Entity class Mensaje
* @author pepes
@MessageDriven(mappedName = "jms/Mensaje", activationConfig = {
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
public class Mensaje implements MessageListener {
/** Creates a new instance of Mensaje */
@Resource
private MessageDrivenContext mdc;
public Mensaje() {
public void onMessage(Message message) {
javax.jms.TextMessage msg = null;
try {
if (message instanceof javax.jms.TextMessage) {
msg = (javax.jms.TextMessage) message;
System.out.println(msg.getText());
} else {
System.out.println("Message of wrong type: "
+ message.getClass().getName());
} catch (javax.jms.JMSException e) {
e.printStackTrace();
mdc.setRollbackOnly();
} catch (Throwable te) {
te.printStackTrace();
{code}
the file prueba.jsp
{code}
<%@page contentType="text/html"%>
<%@page pageEncoding="UTF-8"%>
<%--
The taglib directive below imports the JSTL library. If you uncomment it,
you must also add the JSTL library to the project. The Add Library... action
on Libraries node in Projects view can be used to add the JSTL 1.1 library.
--%>
<%--
<%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
--%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<h1>JSP Page</h1>
<%--
This example uses JSTL, uncomment the taglib directive above.
To test, display the page like this: index.jsp?sayHello=true&name=Murphy
--%>
<%--
<c:if test="${param.sayHello}">
<!-- Let's welcome the user ${param.name} -->
Hello ${param.name}!
</c:if>
--%>
<%
try {
javax.naming.InitialContext ctx = new javax.naming.InitialContext();
org.pepes.publicarRemote publisher = (org.pepes.publicarRemote)ctx.lookup("ejb/publicar");
if (publisher==null) {
System.out.println("INFO: Es null");
else {
System.out.println("INFO: No es null");
publisher.creaMensaje();
} catch (javax.naming.NamingException ex) {
System.out.println("ERROR naming: " + ex.getMessage());
catch (javax.jms.JMSException jmex) {
System.out.println("ERROR jms: " + jmex.getMessage());
catch (java.lang.NullPointerException nullex) {
System.out.println("ERROR null: " + nullex.getMessage());
%>
</body>
</html>
{code}
I think the problem is because i don't put destination address. if it is so, the true where do I put this address?. if not where is the problem?
I hope your help.
Thanks you in advanced.Hi,
Did you create your destinations in your application server? It seems that the destinations such as topics and queues are not created. First you should create them and then start using them.
For example, in here, it says that jndi/Topic is not valid. To check if the destinations are valid or not; you can do it either through the graphical user interface or the command line console. -
Problem with EJB and JMS - Failed to obtain/create connection
hello ejb and jms programmers,
My problem is my topic MDB keep on retrieving the same message when there is a database connection failure. Maybe somebody could help me how to prevent to retrieve the same data?
Given:
- I purposedly turn off the pointbase database because im testing my error handling.
- Im using SJSAS 8 as my application server.
- My message Driven Bean of topic type.
- Im using CMP for my entity bean
Here is the scenario of whats happening - step by step:
1. A separate application publishes a message to JMS queue server
2. My MDB retrieves this message and do some processing then inserts a record (transaction history) in my database
3. But my db is turned off or down
4. My MDB sends a successful processing reply to the JMS queue server
5. Then i noticed that my server.log keeps on growing so when i opened it, the record was not inserted and printed the stacktrace below "RAR5117 : Failed to obtain/create connection. Reason : javax.transaction.SystemException" (complete stacktrace below)
6. I understand the cause of the stacktrace is because the DB is turned off. But what i dont understand is that my MDB keeps on reading the same message. Since my MDB is of topic type, isnt a topic MDB supposedly reads a message only once???
So my questions are:
1. how do i handle insert database error?
2. how can i stop my MDB from processing the same message?
3. any better suggestions?
Thank you in advance :)
leigh
*** more complete stack trace ***
[#|2005-01-09T15:35:57.097+0800|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=17;|JTS5041: The resource manager is doing work outside a global transaction
javax.transaction.xa.XAException
at com.pointbase.xa.xaException.getXAException(Unknown Source)
at com.pointbase.xa.xaConnectionResource.start(Unknown Source)
at com.sun.gjc.spi.XAResourceImpl.start(XAResourceImpl.java:162)
[#|2005-01-09T15:35:57.167+0800|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=17;|RAR5027:Unexpected exception in resource pooling
javax.transaction.SystemException
at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:185)
at com.sun.enterprise.distributedtx.J2EETransaction.enlistResource(J2EETransaction.java:360)
at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.enlistResource(J2EETransactionManagerImpl.java:303)
at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.enlistResource(J2EETransactionManagerOpt.java:115)
[#|2005-01-09T15:35:57.177+0800|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=17;|RAR5117 : Failed to obtain/create connection. Reason : javax.transaction.SystemException|#]
[#|2005-01-09T15:35:57.227+0800|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=17;|RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: javax.transaction.SystemException]|#]
[#|2005-01-09T15:35:57.237+0800|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=17;|EJB5071: Some remote or transactional roll back exception occurred
com.sun.jdo.api.persistence.support.JDODataStoreException: JDO77006: SQL exception: state = null, error code = 0.
NestedException: java.sql.SQLException: Error in allocating a connection. Cause: javax.transaction.SystemException
FailedObjectArray: [[email protected]5ac]
at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.getConnectionInternal(TransactionImpl.java:1444)
at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.getConnection(TransactionImpl.java:1339)Hi annie,
Wherever you are handling database transactions,
you'd not be able to create a Connection if database
is closed (I think you mentioned turning off the
database) then at this condition, you should
certainly throw a System level exception and stop all
processing with some meaningful flow to indicate a
failure (like display message on UI). Even
network problems are handled by exceptions... so I
don't see a reason why you didn't wrap it in the
first place.
Anyway, try handling specific exceptions rather than
the general Exception... this will give you a better
idea of what to do in case of an exception.Yes i know this. I am practicing this in my non-j2ee server applications. But the j2ee app im making, i just pass the db url in the descriptor and the app server automatically creates the connection for my app. So where would i put exception handling?
2. how can i stop my MDB from processing the same
message?Guaranteed delivery is not supposed to stop
processing. It will continue to process the message
after certain intervals till the message is
delivered. You shouldn't deliver it at all, if you
are able to detect that the database is off
The problem here is that my MDB automatically retrieves the message from the JMS queue server. Im not the one retrieving the messages manually.
My assumed behavior of topic MDB is once the a certain MDB retrieves a message it will not retrieve the same message anymore.
thank you in advance.
leigh -
ORABPEL-12165 error while publishing a 77KB message payload to a JMS topic
Our BPEL process reports the above exception when we tried to publish a 23 line PO to a JMS topic with the default partner link settings (on a dev workstation using the OC4J JMS provider). We do not see the above errror manifest itself on smaller size purchase orders (1-6 line orders). The stack trace from the domain long is shown below:
<2006-04-05 16:28:13,390> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> XMLHelper_setJmsMessageHeadersAndPropertiesFromXML: No headers/properties set because element is null
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsProducer_execute: A resource exception occured while producing message
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
ORABPEL-12165
ERRJMS_PROVIDER_ERR.
Could not produce message due to JMS provider error.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:209)
at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:114)
at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:195)
at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:154)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:458)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:647)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:448)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335)
at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.jms.JMSException: storeMessage(ID:Oc4jJMS.Message.OCS1PC.737371:10a6c2453eb:-8000.352,c0:a7:7:1f:24:2c:0:0:29:0:0:0:0:0:0:0:0:2a:1:a:6c:2b:84:11)
at com.evermind.server.jms.JMSUtils.makeJMSException(JMSUtils.java:1844)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1860)
at com.evermind.server.jms.ServerStore.storeMessage(ServerStore.java:757)
at com.evermind.server.jms.ServerStore.enq(ServerStore.java:157)
at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:464)
at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:97)
at com.evermind.server.jms.JMSProvider.enqMessage(JMSProvider.java:574)
at com.evermind.server.jms.EvermindSession.send(EvermindSession.java:1099)
at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:409)
at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:201)
at com.evermind.server.jms.EvermindTopicPublisher.publish(EvermindTopicPublisher.java:77)
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:195)
... 30 morelook into the jms.log - can be found @ $BPEL_HOME/integration\orabpel\system\appserver\oc4j\j2ee\home\log
maybe this gives some more information..
hth clemens -
BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 moreBPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 more -
AppServer crashes. Need help troubleshooting
After following the guidance and completing the installation I have noticed AppServer will crash intermittently. It could happen after 5 mins running or 15. Here's the log in /opt/SUNWappserver/domains/domain1/logs/server.log
[#|2008-10-10T00:08:47.665+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application
server startup complete.|#]
Oct 10, 2008 12:22:23 AM
com.sun.enterprise.admin.servermgmt.launch.ASLauncher buildCommand
INFO:
/usr/jdk/instances/jdk1.5.0/bin/java
-Dcom.sun.aas.instanceRoot=/opt/SUNWappserver/domains/domain1
-Dcom.sun.aas.ClassPathPrefix=
-Dcom.sun.aas.ClassPathSuffix=
-Dcom.sun.aas.ServerClassPath=
-Dcom.sun.aas.classloader.appserverChainJars.ee=
-Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,j2ee-svc.jar
-Dcom.sun.aas.classloader.excludesList=admin-cli.jar,appserv-upgrade.jar,sun-appserv-ant.jar
-Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
-Dcom.sun.aas.classloader.optionalOverrideableChain=webservices-rt.jar,webservices-tools.jar
-Dcom.sun.aas.classloader.serverClassPath.ee=/opt/SUNWappserver/hadb/4.4.3-6/lib/hadbjdbc4.jar,/opt/SUNWappserver/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,/opt/SUNWappserver/hadb/4.4.3-6/lib/dbstate.jar,/opt/SUNWappserver/hadb/4.4.3-6/lib/hadbm.jar,/opt/SUNWappserver/hadb/4.4.3-6/lib/hadbmgt.jar,/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.classloader.serverClassPath=/opt/SUNWappserver/lib/install/applications/jmsra/imqjmsra.jar,/opt/SUNWappserver/imq/lib/jaxm-api.jar,/opt/SUNWappserver/imq/lib/fscontext.jar,/opt/SUNWappserver/imq/lib/imqbroker.jar,/opt/SUNWappserver/imq/lib/imqjmx.jar,/opt/SUNWappserver/lib/ant/lib/ant.jar,/opt/SUNWappserver/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
-Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,jesmf-plugin.jar,/opt/SUNWappserver/hadb/4.4.3-6/lib/dbstate.jar,/opt/SUNWappserver/hadb/4.4.3-6/lib/hadbjdbc4.jar,jgroups-all.jar,/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar
-Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,/usr/jdk/instances/jdk1.5.0/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,com-sun-commons-launcher.jar,com-sun-commons-logging.jar,/opt/SUNWappserver/imq/lib/jaxm-api.jar,/opt/SUNWappserver/imq/lib/fscontext.jar,/opt/SUNWappserver/imq/lib/imqbroker.jar,/opt/SUNWappserver/imq/lib/imqjmx.jar,/opt/SUNWappserver/imq/lib/imqxm.jar,webservices-rt.jar,webservices-tools.jar,mail.jar,appserv-jstl.jar,jmxremote_optional.jar,/opt/SUNWappserver/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar,/opt/SUNWappserver/updatecenter/lib/updatecenter.jar,/opt/SUNWappserver/jbi/lib/jbi.jar,/opt/SUNWappserver/imq/lib/imqjmx.jar,/opt/SUNWappserver/lib/ant/lib/ant.jar,dbschema.jar
-Dcom.sun.aas.configName=server-config
-Dcom.sun.aas.configRoot=/opt/SUNWappserver/config
-Dcom.sun.aas.defaultLogFile=/opt/SUNWappserver/domains/domain1/logs/server.log
-Dcom.sun.aas.domainName=domain1
-Dcom.sun.aas.installRoot=/opt/SUNWappserver
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-Dcom.sun.aas.promptForIdentity=true
-Dcom.sun.appserv.nss.db=/opt/SUNWappserver/domains/domain1/config
-Dcom.sun.appserv.pluggable.features=com.sun.enterprise.ee.server.pluggable.EEPluggableFeatureImpl
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.help,javax.portlet
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Dcom.sun.updatecenter.home=/opt/SUNWappserver/updatecenter
-Ddomain.name=domain1
-Djava.endorsed.dirs=/opt/SUNWappserver/lib/endorsed
-Djava.ext.dirs=/usr/jdk/instances/jdk1.5.0/lib/ext:/usr/jdk/instances/jdk1.5.0/jre/lib/ext:/opt/SUNWappserver/domains/domain1/lib/ext:/opt/SUNWappserver/javadb/lib:/opt/SUNWappserver/lib/jdbcdrivers
-Djava.library.path=/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib
-Djava.security.auth.login.config=/opt/SUNWappserver/domains/domain1/config/login.conf
-Djava.security.manager
-Djava.security.policy=/opt/SUNWappserver/domains/domain1/config/server.policy
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Djavax.management.builder.initial=com.sun.enterprise.ee.admin.AppServerMBeanServerBuilder
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djmx.invoke.getters=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
-server
-XX:+UnlockDiagnosticVMOptions
-XX:MaxPermSize=192m
-Xmx512m
-XX:NewRatio=2
-XX:+LogVMOutput
-XX:LogFile=/opt/SUNWappserver/domains/domain1/logs/jvm.log
-cp
/opt/SUNWappserver/lib/jhall.jar:/opt/SUNWappserver/lib/appserv-launch.jar
com.sun.enterprise.server.PELaunch
start
[#|2008-10-10T00:22:23.753+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting
Sun Java System Application Server 9.1_01 (build b09d-fcs) ...|#]
[#|2008-10-10T00:22:23.829+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=11;_ThreadName=pool-1-thread-2;com.sun.enterprise.interceptor.DynamicInterceptor;|MBeanServer
started: com.sun.enterprise.interceptor.DynamicInterceptor|#]
[#|2008-10-10T00:22:24.686+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java
HotSpot(TM) Server VM;1.5.0_16;Sun Microsystems Inc.;|CORE5076: Using
[Java HotSpot(TM) Server VM, Version 1.5.0_16] from [Sun Microsystems
Inc.]|#]
[#|2008-10-10T00:22:24.744+0100|INFO|sun-appserver9.1|javax.enterprise.resource.jms|_ThreadID=12;_ThreadName=pool-1-thread-7;|Using
MQ RA for Broker lifecycle control|#]
[#|2008-10-10T00:22:24.798+0100|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=13;_ThreadName=pool-1-thread-4;|SEC1001:
Security Manager is ON.|#]
[#|2008-10-10T00:22:26.158+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=10;_ThreadName=main;|/opt/SUNWappserver/domains/domain1/config/.__com_sun_appserv_pid|#]
[#|2008-10-10T00:22:26.974+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:SunoneInterceptor
is now enabled|#]
[#|2008-10-10T00:22:27.277+0100|INFO|sun-appserver9.1|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2008-10-10T00:22:28.727+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=10;_ThreadName=main;|EJBSCLookup::
sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false|#]
[#|2008-10-10T00:22:29.694+0100|INFO|sun-appserver9.1|javax.enterprise.system.core.transaction|_ThreadID=10;_ThreadName=main;3700;|JTS5014:
Recoverable JTS instance, serverId = [3700]|#]
[#|2008-10-10T00:22:30.051+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079:
Initialization of AMX MBeans started|#]
[#|2008-10-10T00:22:30.510+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=Thread-16;service:jmx:rmi:///jndi/rmi://one.mydomain.com:8686/jmxrmi;|ADM1504:
Here is the JMXServiceURL for the Standard JMXConnectorServer:
[service:jmx:rmi:///jndi/rmi://one.mydomain.com:8686/jmxrmi].
This is where the remote administrative clients should connect using
the standard JMX connectors|#]
[#|2008-10-10T00:22:30.511+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=Thread-16;true;|ADM1506:
Status of Standard JMX Connector: Active = [true]|#]
[#|2008-10-10T00:22:30.922+0100|INFO|sun-appserver9.1|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;|JMS
Service Connection URL is :mq://one.mydomain.com:7676/|#]
[#|2008-10-10T00:22:30.944+0100|INFO|sun-appserver9.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101:
SJSMQ JMS Resource Adapter starting...|#]
[#|2008-10-10T00:22:31.481+0100|INFO|sun-appserver9.1|com.sun.mfwk.Mfwk
MfConfig|_ThreadID=10;_ThreadName=main;|url:
jar:file:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class|#]
[#|2008-10-10T00:22:31.482+0100|INFO|sun-appserver9.1|com.sun.mfwk.Mfwk
MfConfig|_ThreadID=10;_ThreadName=main;|"mfwk.multicast.disableloopback"
set to false|#]
[#|2008-10-10T00:22:31.483+0100|INFO|sun-appserver9.1|com.sun.mfwk.Mfwk
MfConfig|_ThreadID=10;_ThreadName=main;|url:
jar:file:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class|#]
[#|2008-10-10T00:22:31.483+0100|INFO|sun-appserver9.1|com.sun.mfwk|_ThreadID=10;_ThreadName=main;|LogFile
is: //var/opt/SUNWmfwk/logs/instrum.%g|#]
[#|2008-10-10T00:22:32.862+0100|INFO|sun-appserver9.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_EB1101:
EMBEDDED broker started with code =0|#]
[#|2008-10-10T00:22:32.865+0100|INFO|sun-appserver9.1|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101:
SJSMQ JMSRA Started:DIRECT|#]
[#|2008-10-10T00:22:33.447+0100|INFO|sun-appserver9.1|javax.enterprise.resource.corba|_ThreadID=16;_ThreadName=pool-1-thread-3;|POARemoteRefFactory
checking if SFSBVersionPolicy need to be added|#]
[#|2008-10-10T00:22:33.448+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=16;_ThreadName=pool-1-thread-3;|EJBSCLookup::
sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false|#]
[#|2008-10-10T00:22:33.448+0100|INFO|sun-appserver9.1|javax.enterprise.resource.corba|_ThreadID=16;_ThreadName=pool-1-thread-3;|POARemoteRefFactory
addSFSBVersionPolicy? false|#]
[#|2008-10-10T00:22:33.449+0100|INFO|sun-appserver9.1|javax.enterprise.resource.corba|_ThreadID=16;_ThreadName=pool-1-thread-3;|POARemoteRefFactory
checking if SFSBVersionPolicy need to be added|#]
[#|2008-10-10T00:22:33.450+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=16;_ThreadName=pool-1-thread-3;|EJBSCLookup::
sc.getEjbContainerAvailabilityEnabledFromConfig() ==> false|#]
[#|2008-10-10T00:22:33.450+0100|INFO|sun-appserver9.1|javax.enterprise.resource.corba|_ThreadID=16;_ThreadName=pool-1-thread-3;|POARemoteRefFactory
addSFSBVersionPolicy? false|#]
[#|2008-10-10T00:22:33.612+0100|INFO|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=16;_ThreadName=pool-1-thread-3;MEjbApp;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2008-10-10T00:22:34.000+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=pool-1-thread-14;jdbc/__TimerPool;|EJB5109:EJB
Timer Service started successfully for datasource
[jdbc/__TimerPool]|#]
[#|2008-10-10T00:22:34.001+0100|INFO|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=pool-1-thread-14;__ejb_container_timer_app;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2008-10-10T00:22:34.080+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0302:
Starting Sun-Java-System/Application-Server.|#]
[#|2008-10-10T00:22:34.123+0100|INFO|sun-appserver9.1|com.sun.jbi.framework|_ThreadID=17;_ThreadName=pool-1-thread-14;|JBIFW0010:
JBI framework ready to accept requests.|#]
[#|2008-10-10T00:22:34.398+0100|INFO|sun-appserver9.1|GRIZZLY|_ThreadID=10;_ThreadName=main;|Enabling
Grizzly ARP Comet support.|#]
[#|2008-10-10T00:22:34.459+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;80;|WEB0712:
Starting Sun-Java-System/Application-Server HTTP/1.1 on 80|#]
[#|2008-10-10T00:22:34.479+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|Enabling
Grizzly ARP Comet support.|#]
[#|2008-10-10T00:22:34.537+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;8181;|WEB0712:
Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181|#]
[#|2008-10-10T00:22:34.555+0100|INFO|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;4848;|WEB0712:
Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848|#]
[#|2008-10-10T00:22:34.929+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
---Initializing iWC Application Context---|#]
[#|2008-10-10T00:22:34.951+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: com.sun.faces.injectionProvider Param Value:
com.sun.faces.vendor.GlassFishInjectionProvider|#]
[#|2008-10-10T00:22:34.951+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: com.sun.faces.validateXml Param Value: true|#]
[#|2008-10-10T00:22:34.951+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: RMI_CONNECTOR_PORT Param Value: 50005|#]
[#|2008-10-10T00:22:34.952+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: CONFIG_FILE_FORMAT Param Value: xml|#]
[#|2008-10-10T00:22:34.952+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: VALIDATE_CONFIG_SCHEMA Param Value: true|#]
[#|2008-10-10T00:22:34.952+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: RMI_REGISTRY_PORT Param Value: 50005|#]
[#|2008-10-10T00:22:34.952+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: CONFIG_LOCATION Param Value: /var/opt/sun/comms/iwc/config|#]
[#|2008-10-10T00:22:34.952+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: com.sun.faces.forceLoadConfiguration Param Value: true|#]
[#|2008-10-10T00:22:34.953+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Context Param: CONFIG_FILE_SERVICE_ADAPTER_CLASSNAME Param Value:
com.sun.comms.client.config.sun.SunCommsXMLConfigService|#]
[#|2008-10-10T00:22:34.953+0100|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=16;_ThreadName=pool-1-thread-3;|
Loading the Application Configuration...|#]
[#|2008-10-10T00:22:42.318+0100|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=16;_ThreadName=pool-1-thread-3;_RequestID=a737b8f7-acb9-49fe-8df4-a9e5c620eebf;|log4j:WARN
No appenders could be found for logger
(org.apache.commons.digester.Digester).|#]
[#|2008-10-10T00:22:42.322+0100|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=16;_ThreadName=pool-1-thread-3;_RequestID=a737b8f7-acb9-49fe-8df4-a9e5c620eebf;|
log4j:WARN Please initialize the log4j system properly.|#]
[#|2008-10-10T00:22:42.841+0100|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=16;_ThreadName=pool-1-thread-3;_RequestID=a737b8f7-acb9-49fe-8df4-a9e5c620eebf;|
Missing native library key in web.xml : httpbind.library.checkpermission|#]
[#|2008-10-10T00:22:44.867+0100|INFO|sun-appserver9.1|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|SMGT0007:
Self Management Rules service is enabled|#]
[#|2008-10-10T00:22:44.898+0100|WARNING|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=10;_ThreadName=main;_RequestID=c8c1742d-f271-461d-83d9-4abcf7186b7a;|EJBLifeCycle:
Automatic timer migration component not enabled for DAS instance|#]Not sure if I've done it correctly but here goes:
/usr/bin/pstack /var/cores/rds.one.mydomain.com.14236.1223658132.core
core '/var/cores/rds.one.mydomain.com.14236.1223658132.core' of 14236: /usr/sadm/lib/wbem/rds -a -t 30000 -i 1000 -f /var/run/rds_db -m -L /v
----------------- lwp# 1 / thread# 1 --------------------
fffffd7fff362f1a ___nanosleep () + a
00000000004050fa ???????? ()
00000000004054e8 main () + 2e8
000000000040439c _start () + 6c
----------------- lwp# 2 / thread# 2 --------------------
0000000000408836 wr_error () + 56
00000000004044b9 ???????? ()
00000000004045f5 ???????? ()
0000000000404690 ???????? ()
00000000004048ae ???????? ()
fffffd7fff360bfb _thr_setup () + 5b
fffffd7fff360e30 _lwp_start ()
----------------- lwp# 3 / thread# 3 --------------------
fffffd7fff363b4a __pollsys () + a
fffffd7fff30a362 poll () + 52
0000000000405bdf napms () + f
0000000000404f62 ???????? ()
fffffd7fff360bfb _thr_setup () + 5b
fffffd7fff360e30 _lwp_start ()I tried going in to "one.mydomain.com/iwc" and received 'Unable to connect' in Firefox although it used to display login prompt before. Application Server appears to be running.
Maybe you are looking for
-
Mail wont open after snow leopard update
Mail refuses to open after update,when initated it flashes in the tray then disappears,has apple a fix for this problem? Or admits it exists. Thanks
-
Equium L10 300: DVD burning & S-Video question
I have a Equium L10 300. I have 2 questions. 1: It says that it is a MULTI recorder but it does not burn to DVD+RW, is this correct ? 2: When I connect to the television via the S-video cable to play a slide show from the laptop the TV screen is blan
-
How to hide menu drop downs layout
Can I hide the menu drop downs on my layout pages? They interfere with laying out text and images.
-
I have updated my service pack for windows to Service Pack 3 for XP including any other updates needed for windows. i was already having problems with itunes freezing on me so i completely uninstalled the program and anything that was related to it t
-
How can i sync notes on ipad and iphone using itunes?
how can i sync notes on ipad and iphone using itunes? it used to work with me before upgrading to mountain lion.