Some methods not working in EJB 3.0 stateless session bean

Hi,
I am trying to build an application with EJB 3.0 stateless session bean in weblogic 10. In that during build (using ant 1.6) it showing error as one of the ejb-class should have anotataion as @stateless, @stateful or @messageDiven
But i have given it corrrectly.
When I comment some of the methods the same bean is working fine. While i have annoatated some of the methods with @transaction attribute annotataion.
So, should i write all those methods there any particular order or what.
Can anybody pls tell me, what can be the problem as weblogic.appc is giving such error?

Similar Messages

Odd marshalling problems with EJB 3.0 stateless session bean

Hello,
I began encountering marshalling exceptions when invoking methods on a previously functionining facade bean. The problem seems to be almost arbitrary, in that certain packages receive marshalling exceptions, while others do not (my main client started failing, but then I realized that a simple test class was still working, along with oddly JSFs that invoke that main client, which fails outside of that scope). Is there some config issue with stateless session beans (in 3.0) that I might be missing? There are no duplicate versions of these class; they have not been modified; they've been compiled with the current IDE. Any help would be appreciated. Thanks.
full stack trace:
com.evermind.reflect.UndeclaredExceptionTypeException: oracle.oc4j.rmi.OracleRemoteException
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
oracle.oc4j.rmi.OracleRemoteException: Invocation error: java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:142)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
 Nested exception is:
java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
oracle.oc4j.rmi.OracleRemoteException: Invocation error: java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:142)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
 Nested exception is:
java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)

Hello,
I began encountering marshalling exceptions when invoking methods on a previously functionining facade bean. The problem seems to be almost arbitrary, in that certain packages receive marshalling exceptions, while others do not (my main client started failing, but then I realized that a simple test class was still working, along with oddly JSFs that invoke that main client, which fails outside of that scope). Is there some config issue with stateless session beans (in 3.0) that I might be missing? There are no duplicate versions of these class; they have not been modified; they've been compiled with the current IDE. Any help would be appreciated. Thanks.
full stack trace:
com.evermind.reflect.UndeclaredExceptionTypeException: oracle.oc4j.rmi.OracleRemoteException
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
oracle.oc4j.rmi.OracleRemoteException: Invocation error: java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:142)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
 Nested exception is:
java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
oracle.oc4j.rmi.OracleRemoteException: Invocation error: java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:142)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)
 Nested exception is:
java.rmi.UnmarshalException: Error deserializing return-value: java.io.InvalidClassException: com.jwt.gui.menus.persistence.ViewRight; local class incompatible: stream classdesc serialVersionUID = 2365320765203750319, local class serialVersionUID = -8750611773395720631
 at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
 at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:128)
 at com.evermind.server.rmi.RMIClientConnection.obtainRemoteMethodResponse(RMIClientConnection.java:472)
 at com.evermind.server.rmi.RMIClientConnection.invokeMethod(RMIClientConnection.java:416)
 at com.evermind.server.rmi.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:63)
 at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:28)
 at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
 at __Proxy1.findAllViewRight(Unknown Source)
 at com.jwt.gui.menus.beans.ViewRightBean.<init>(ViewRightBean.java:34)
 at com.jwt.gui.menus.beans.ViewRightBean.main(ViewRightBean.java:63)

NameNotFoundException EJB 3.0 Stateless Session Bean

Hi i am new to ejb 3.0 as well as ejb actually. I encountered an error trying out a small stateless session bean application.
23:15:02,312 ERROR [STDERR] javax.naming.NameNotFoundException: com.afis.ct.ri.session.ejb.ReportIncidentSession not bound
23:15:02,312 ERROR [STDERR]      at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
23:15:02,312 ERROR [STDERR]      at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
23:15:02,312 ERROR [STDERR]      at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
23:15:02,312 ERROR [STDERR]      at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
23:15:02,312 ERROR [STDERR]      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
23:15:02,312 ERROR [STDERR]      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
23:15:02,312 ERROR [STDERR]      at javax.naming.InitialContext.lookup(InitialContext.java:351)
23:15:02,312 ERROR [STDERR]      at com.afis.ct.servlets.ri.ValidateIdentityServlet.validateIdentity(ValidateIdentityServlet.java:64)
23:15:02,312 ERROR [STDERR]      at com.afis.ct.servlets.ri.ValidateIdentityServlet.processRequest(ValidateIdentityServlet.java:35)
23:15:02,312 ERROR [STDERR]      at com.afis.ct.servlets.ri.ValidateIdentityServlet.doGet(ValidateIdentityServlet.java:19)
23:15:02,312 ERROR [STDERR]      at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
23:15:02,312 ERROR [STDERR]      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
23:15:02,328 ERROR [STDERR]      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
23:15:02,328 ERROR [STDERR]      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
23:15:02,328 ERROR [STDERR]      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
23:15:02,328 ERROR [STDERR]      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
23:15:02,328 ERROR [STDERR]      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
23:15:02,328 ERROR [STDERR]      at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
23:15:02,328 ERROR [STDERR]      at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
23:15:02,328 ERROR [STDERR]      at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
23:15:02,328 ERROR [STDERR]      at java.lang.Thread.run(Thread.java:595)My remote interface looks like
package com.afis.ct.ri.session.ejb;
import javax.ejb.Remote;
@Remote
public interface ReportIncidentSession {
     public boolean isIdentityValid(String identity);
}My bean looks like
package com.afis.ct.ri.session.ejb;
import javax.ejb.Stateless;
@Stateless
public class ReportIncidentSessionBean implements ReportIncidentSession {
     public ReportIncidentSessionBean() {
          super();
     public boolean isIdentityValid(String identity) {
          return true;
}Finally i am calling from a servlet which is part of a web application under the same hood(ear) as the ejb jar file.
InitialContext ctx=new InitialContext();
               ReportIncidentSession session=(ReportIncidentSession)ctx.lookup(ReportIncidentSession.class.getName());
                              return session.isIdentityValid(identity);I have done nothing more than making sure there is no compilation error, and i feel some mandatory steps are missing.. So thanks for any help!
Marvelous.

Hi DRS, i tried your recommendation and injected the following on top of my servlet class:
EJB(name="ReportIncidentSessionBean", businessInterface=ReportIncidentSession.class)
public class ValidateIdentityServlet extends HttpServlet implements
          ValidateIdentity {The original beanInterface you mentioned had an error.
And upon deployment, JBoss wasn't able to generate a deployment descriptor hinting at the annotations.
23:50:08,765 ERROR [MainDeployer] Could not create deployment: file:/C:/Program Files/jboss-4.0.4.GA/server/Marvelous/deploy/Avian Flu Information System.ear/Avian Flu Information System Web.war/
java.lang.UnsupportedOperationException: FIXME: should ignore annotations for missing classes
     at org.jboss.lang.AnnotationHelper.getAnnotations(AnnotationHelper.java:98)
     at org.jboss.lang.AnnotationHelper.getAnnotation(AnnotationHelper.java:75)
     at org.jboss.lang.AnnotationHelper.isAnnotationPresent(AnnotationHelper.java:60)
     at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:152)
     at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)
     at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:66)
     at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
     at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy49.create(Unknown Source)
     at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
     at org.jboss.deployment.MainDeployer.create(MainDeployer.java:943)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
     at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy6.deploy(Unknown Source)
     at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
     at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)Your input is greatly appreciated!

Calling EJB 3.0 Stateless Session Bean

Dear all,
I created a stateless session bean with a hello world method on it. Now i want to call the method from a BeanDecorator class, through a getter metod. When i use the jndi lookup in my getter, i can call the helloWorld method without a problem. However, when i dont use the jndi lookup, and only use the @EJB annotation, i always get a nullpointer.
This is working:
InitialContext ic = new InitialContext();
test = (TestLocal)ic.lookup("test.be/ear~bd/LOCAL/TestBean/"+TestLocal.class.getName());
test.helloWorld()
This gives nullpointer:
@EJB
private TestLocal test;
test.helloWorld();
What is the correct way to consume session beans without having to explicitly code the jndi lookup?
Kind regards.

Hi,
any annotation like this can be used only in "managed classes" like Session Beans, Servlets etc. Managed classes are those classes managed by the J2EE server. Managed here means, lifetime controlled by server.
You can find this in J2EE specification.
Frank

Some PDFs not working in Preview. Mac created PDFS work but windows created PDFS dont

Some PDFs not working in Preview. I installed adobe reader and then deleted it because the software was aweful and PDFs have been haveing issues ever since. I can open up PDFs created on my Mac in preview just fine...
But when I try and open a PDF created on a windows computer it says:
"Please wait...
If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/products/acrobat/readstep2.html.
For more assistance with Adobe Reader visit http://www.adobe.com/support/products/ acrreader.html.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. "
I am not sure why where the PDF was created would make a difference but couldnt help but notice that was the difference between the PDF files that work and the ones that give that message. I can view the PDFs on a windows computer just fine and never had issues untill adobe, it seems to have messed up PDFs on my Mac and I am so frustrated with them. I have searched my computer for any remaining adobe files, deleted them and restarted my computer but I am still getting this message.

Uninstall Adobe Reader's plug-in.
Remove the following two files from /Library/Internet Plug-Ins/:
AdobePDFViewer.plugin
AdobePDFViewerNPAPI.plugin
Open Safari Preferences > Extensions. Do you see AdobePDFViewer? If yes. disable.
Log out/in and test.
Another option is to download and install this plugin. Schubert|it PDF Browser Plugin . PDF Browser Plugin 2 is free for not-for-profit activities if used at home or at educational institutions.
http://www.schubert-it.com/pluginpdf/

Keyboard: some keys not working

Some keys not working. Need help/suggestions. Not great with computers so PLEASE give details/steps re: how to do what you suggest - thanks!
Details: intel based iMac running snow leopard 10.6.8. Apple wireless/bluetooth keyboard (came with the iMac).
Some keys suddenly stopped working: space, tab, capLock, option key to the right of space bar (one on the left works), down arrow
The problem happens in various programs (safari, pages, etc)
The keyboard is fine on another iMac
A different keyboard is fine on this/the involved iMac
(nutshell: keyboard works fine - computer works fine, unless they're together)
Here's what's been tried/checked:
-checked the settings for universal access ("mouse keys" are off) and checked for any bluetooth keyboard shortcuts.
-in system preferences "speech" is not set for "speak selected text when the key is pressed" - this is not checked/selected
-tried creating a new user but had the same issue so it's computer-wide rather than just a user account
-removed the keyboard and reconnected (using the +/- signs and "disconnect" and putting in a new code of numbers to pair keyboard)
-language/text is set for english
-did the keyboard viewer and the keys in question did NOT highlight when pressed (but don't forget the entire keyboard is fine on a different computer so thekeys aren't the issue)
-"slow keys" is turned off re: keyboard in system preferences.
Any help is welcomed. It's frustrating knowing the keyboard works, just not with this computer. Please help. Many thanks!

yes - not sure how this works...if you can see my original post there are a lot of details in there. If you can't...
nutshell: the keyboard works on a different iMac
             a different keyboard works on this/the involved iMac
             I tried to create a different user and the keyboard still does not work so it is computer-wide
             I also removed the keyboard from the computer (using the +/- symbols and disconnecting and then repairing it. The problem remained
Thanks for any help. It's crazy that the keyboard is fine and the computer is fine but together, there's the problem.
Thank you!!!

I have downloaded a trial version of Dreamweaver CS6 to my MacBook. Why do some features not work?

I have downloaded a trial version of Dreamweaver CS6 to my MacBook. Why do some features not work? I have OSX 10.6.8. I am using this trial version for a class I am taking on coding webpages using Dreamweaver. there are features I am using in class that will not open up or appear as options when I use the trial version. Are certain features locked out until I buy a copy or download a purchased copy?

Trial versions have no functional limitations, though your setup/situation might not be supportive of all functionality. You'll need to identify specific issues to get help with them. You should be posting in the DW forum instead of here if your issue does not have to do with downloading/installing.

Wireless keyboard some keys not working

wireless keyboard some keys not working need help

Please do a SMC reset, if that does not work the first time please do it 2-3 more times. You can find instructions at:
https://discussions.apple.com/docs/DOC-3603

After Method not work

Hello guys,
I need your help.
In activity step I added one method in "Methods AFTER Work Item Execution (Modal Call)", but this method not work after complete the workitem.
This method run in background, and insert data in one table.
My workflow use BUS1001006 object type, and this method too.
Any idea?
Thanks!!!
Kleber

Hi Arghadip!!!
Now it's work fine!!! Thanks!!!
Please... more one question...
In my method, I need the value of the element _Workitem.WorkitemStatus.
It's possible:
===========================================================
swc_get_element container '_Workitem.WorkitemStatus' vl_status.
===========================================================
or
===========================================================
swc_get_element container '_Workitem-WorkitemStatus' vl_status.
===========================================================
How I do this?
Thank a lot!!!
Kleber

HT1977 I bought apps. My kid delet that after few weeks. Then I have downloaded to same ipad. But some functions not working.

I purchase some apps, my son deleted some. But I have download again from cloud. But some functions not working ask me to pay again. How can I use functions without paying again. Thank you

Search around on the app settings and see if there's a "Restore purchases" option.

Some apps not working on osx

some apps not working in osx

Your comment is roughly like going to the doctor and saying "I hurt".
How are we supposed to help you without a whole lot more information? What apps? How are they misbehaving?

EJB 3.1new instance of stateless session bean not created on new invocation

I am using Netbeans 6.8 bundle that comes with JAVA EE 6. I have created a web application then created restful web services and then created few stateless session beans (with local interfaces) that are invoked from restful web services. From the browser, when I call the url with get method, restful web services are being invoked and they in turn calls stateless session beans and does the appropriate business logic. While testing, I observed that for every new url call from the browser, the same bean is being invoked. I tested this by adding a instance variable vector and adding one item ('test") to the vector in bean's method. My understanding is that on every bean's method invocation the vector should have only one item. However, the vector is growing with many "test" items. I am literally confused, not sure this is the way it is supposed to work. I tried to invoke bean's method from restful web service by using both dependency injection and jndi look up, both instances the vector is growing with many "test" items.
I would really appreciate if some body gives me more insight.

I appreciate your answers. There is a strong reason for posting this question. Basically, I am using JPA and using stateless session beans to invoke database calls. In the bean I am using the following code for entity manager.
@PersistenceContext(unitName = "AsgProtocolServerPU")
private EntityManager em;
I have noticed very strange scenario while getting records. From the application, I have obtained few records of a table. Then, I manually deleted few records from the table. Very strangely, I have obtained the deleted records during my next call to bean. After 2 hours, I tested the same and did not get those records. This is not consistent.
I am totally confused. I am just wondering this is happening because I made beans local (not remote) and placed them in the web application (Java EE6 allows this). I am not sure whether this is JPA related issue or beans issue.

Stateless Session Bean + EJB Question + Jboss

Hello,
If I have a stateless session bean on a linux machine and it works locally what do i need to do to access a method in the session bean from a remote windows machine.
I would like to be able to execute my client jar file on a windows machine and have it access the jboss server on the linux machine. what do i need to do?
i have the session bean working locally on both windows and linux machine. do i need to to have a JSP/Servlet to access the session bean? can the session bean not be accessed directly? what should my classpath look like? do I need to include extra jar files in my client jar file.?
Thanks,
Joyce

Thanks guys for the help but I am still a little lost.
My Client windows machine has the client jar file and all the other jar files. This is my client class
package helloworld.client;
import javax.naming.Context;
import javax.naming.InitialContext;
import java.util.Hashtable;
import java.util.Properties;
import helloworld.interfaces.HelloWorldHome;
import helloworld.interfaces.HelloWorld;
public class HelloClient
 public static void main(String[] args)
 Hashtable prop = new Hashtable();
 prop.put ("java.naming.factory.url.pkgs","org.jboss.naming:org.jnp.interfaces");
 prop.put ("java.naming.provider.url","jnp://172.16.220.160:1099");
 prop.put ("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
 try
 Context ctx = new InitialContext(prop);
 Object obj = ctx.lookup("ejb/helloworld/HelloWorld");
 System.out.println(obj);
 HelloWorldHome home = (HelloWorldHome)javax.rmi.PortableRemoteObject.narrow(obj, HelloWorldHome.class);
 HelloWorld helloWorld = home.create();
 String str = helloWorld.sayHelloEJB("JOYCE is COOL");
 System.out.println(str);
 helloWorld.remove();
 catch(Exception e)
 e.printStackTrace();
I get a NullPointer ie the home object is null. The IP address is the IP of the Linux machine that has Jboss running on.
Questions are:
1. Do I need to have Tomcat running on my client machine if I am to connect via HTTP? Does this alter my client code.?
2. My JNDI lookup is what is causing the problem. Does my jboss.xml and my ejb-jar.jar look okay to you.
jboss.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS//EN" "http://www.jboss.org/j2ee/dtd/jboss.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>helloworld/HelloWorld</ejb-name>
<jndi-name>ejb/helloworld/HelloWorld</jndi-name>
</session>
</enterprise-beans>
<resource-managers>
</resource-managers>
</jboss>
ejb-jar.jar
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<description>No Description.</description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>

<session >
<description><![CDATA[No Description.]]></description>
<ejb-name>helloworld/HelloWorld</ejb-name>
<home>helloworld.interfaces.HelloWorldHome</home>
<remote>helloworld.interfaces.HelloWorld</remote>
<ejb-class>helloworld.session.HelloWorldBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
</session>





</enterprise-beans>


<assembly-descriptor >



</assembly-descriptor>
</ejb-jar>
Do I need RMI ? Do I need to concern myself with CORBA? All Im looking for is a step by step to understanding what I need to configure? Is their some way I can debug?
Thanks alot,
Joyce

Not be able to obtain a transacted session within stateless session bean

I need some assistance on creating a transacted session. For some reason while within a stateless session bean, I am unable to create a transacted session even though I'm specifying to create the transacted queue session. Can anyone provide any assistance to me on this? It would be much appreciated.
Here is the code snippets involved with the problem:
Code snipet from ejb-jar.xml:
<session>
<display-name>Initial Request</display-name>
<ejb-name>InitialRequestBean</ejb-name>
<ejb-class>com.raytheon.rds.jms.InitialRequestBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
Code from stateless session bean:
static Logger logger;
private QueueConnectionFactory connectionFactory;
private SessionContext sc;
private Queue requestQueue;
public String processRequest(String msgBody)
logger.log(Level.INFO, "In processRequest(String).", msgBody);
QueueConnection con = null;
QueueSession session = null;
QueueSender sender = null;
TextMessage message = null;
String messageID = null;
QueueReceiver receiver = null;
TemporaryQueue replyQueue = null;
boolean transacted = false;
try
//Create the infrastructure (ie. The connection & the session)
logger.log(Level.FINE, "Creating connection");
con = connectionFactory.createQueueConnection();
logger.log(Level.FINE, "Creating session");
session = con.createQueueSession(true, Session.AUTO_ACKNOWLEDGE);
//Note: This line above was changed in all possible permutation and still didn't work such as using Session.SESSION_TRANSACTED
transacted = session.getTransacted();
logger.log(Level.FINE, "Is session transacted? : " + transacted);
//Note: This line above is constantly saying false
//Now first, setup the temporary reply queue and its listener
replyQueue = session.createTemporaryQueue();
logger.log(Level.FINE, "Creating receiver/consumer");
receiver = session.createReceiver(replyQueue);
con.start();
//Now create the requestor that will make the request message and put it on the request queue
logger.log(Level.FINE, "Creating Requestor/Producer");
sender = session.createSender(requestQueue);
//Now create the message and make sure that you put the "JMSReplyTo" property to the temporary response queue we just created
message = session.createTextMessage();
message.setJMSReplyTo(replyQueue);
logger.log(Level.FINE, "Created message: " + message.getJMSMessageID());
//Now add the actual info you want to send
message.setText(msgBody);
//Now send the message
logger.log(Level.INFO, "Sending message: " + message.getText());
sender.send(message);
//Now wait until we get a response
logger.log(Level.FINE, "Waiting for the response message");
Message responseMsg = receiver.receive(20000); //Toggle the "0" to specify timeout in millisectionds
//Process the message
logger.log(Level.FINE, "Processing the response message");
if(null != responseMsg)
logger.log(Level.FINE, "responseMsg is : " + responseMsg.toString());
messageID = processMessage(responseMsg);
logger.log(Level.FINE, "Response is : " + messageID);
//close the connection
logger.log(Level.FINE, "Stopping the connection");
con.stop();
catch (Throwable t)
// JMSException could be thrown
logger.log(Level.SEVERE, "Exception Thrown in sendRequest: ", t);
sc.setRollbackOnly();
finally
//Close the sender
if (sender != null)
try
logger.log(Level.FINE, "Closing the sender");
sender.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the sender to the request queue: ", e);
else
logger.log(Level.FINE, "Sender is already closed.");
//Close the receiver
if (receiver != null)
try
logger.log(Level.FINE, "Closing the receiver");
receiver.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the receiver to the request queue: ", e);
else
logger.log(Level.FINE, "Receiver is already closed.");
//Close the session
if (session != null)
try
logger.log(Level.FINE, "Closing the session");
session.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the session to the request queue: ", e);
else
logger.log(Level.FINE, "Session is already closed.");
//Close the connection
if (con != null)
try
logger.log(Level.FINE, "Closing the connection");
con.close();
catch (JMSException e)
logger.log(Level.WARNING, "JMSException Thrown when trying to close the connection to the reply queue: ", e);
else
logger.log(Level.FINE, "Connection is already closed.");
return messageID;
}

I found the answer through lots of painful searching.
http://blogs.sun.com/fkieviet/entry/request_reply_from_an_ejb
This weblog from Frank Kieviet from a sun blog explains what's happening behind the scenes.
Then I proceeded to create a Bean-Managed Transaction out of my EJB, which is using EJB 3.0. This requires the tag:
@TransactionManagement(value= TransactionManagementType.BEAN)
Note: I got this information from http://download.oracle.com/docs/cd/B31017_01/web.1013/b28221/servtran001.htm#BAJIBAFF
Then I just added the code specified in Frank's blog and everything is working now. The main portion of the code looks like this now:
//begin the user transaction
ctx.getUserTransaction().begin();
//Create the infrastructure (ie. The connection & the session)
logger.log(Level.FINE, "Creating connection");
con = connectionFactory.createQueueConnection();
//Create the session
logger.log(Level.FINE, "Creating session");
session = con.createQueueSession(false, Session.SESSION_TRANSACTED);
transacted = session.getTransacted();
logger.log(Level.FINE, "Is session transacted? : " + transacted);
//Now create the sender that will make the request message and put it on the request queue
logger.log(Level.FINE, "Creating Sender");
sender = session.createSender(requestQueue);
//Now create the message
message = session.createTextMessage();
//Now add the actual info you want to send
message.setText(msgBody);
logger.log(Level.FINE, "Created message: " + message.getJMSMessageID());
//Now first, setup the temporary reply queue and its listener
replyQueue = session.createTemporaryQueue();
if(null != replyQueue)
logger.log(Level.FINE, "Created temporary queue: " + replyQueue.getQueueName());
else
logger.log(Level.FINE, "Temporary Queue could not be created.");
//make sure that you put the "JMSReplyTo" property to the temporary response queue we just created
message.setJMSReplyTo(replyQueue);
//Now send the message
logger.log(Level.INFO, "Sending message: " + message.getText());
sender.send(message);
//Now start the connection
logger.log(Level.FINE, "Starting the connection");
con.start();
//commit the changes
ctx.getUserTransaction().commit();
ctx.getUserTransaction().begin();
//Create the receiver
logger.log(Level.FINE, "Creating Receiver");
receiver = session.createReceiver(replyQueue);
//Now wait until we get a response
logger.log(Level.FINE, "Waiting for the response message");
Message responseMsg = receiver.receive(20000); //Toggle the "0" to specify timeout in millisectionds
//Process the message
logger.log(Level.FINE, "Processing the response message");
if(null != responseMsg)
logger.log(Level.FINE, "responseMsg is : " + responseMsg.toString());
else
logger.log(Level.FINE, "No response came back.");
messageID = processMessage(responseMsg);
logger.log(Level.FINE, "Response is : " + messageID);
logger.log(Level.FINE, "Transaction is complete");
//commit the changes
ctx.getUserTransaction().commit();

Transaction is not Rolling Back in Stateless Session Bean

 Hi,
 I am using UserTransaction in Stateless Session bean .
 Transaction is not rolling back.
 The following code is writen in stateless session bean. In UserTransaction i am
 calling Two methods of another stateless session bean.
 The problem is if doJob2() method fails, doJob1() method is rolling back. These
 two methods consist of SQL statement with different Connection Object from TXDataSource.And
 session bean(TestSession) is set to CMT, attribute as "Required".
 try{
 Context ictx=new InitialContext();
 TestHome home=(TestHome)ictx.lookup("TestSession");
 utx = sessionCtx.getUserTransaction();
 utx.begin();
 TestRemote remote=home.create();
 remote.doJob1();
 remote.doJob2();
 utx.commit();
 }catch(Exception e)
 try{
 utx.rollback();
 }catch(Exception ex)
 System.out.println("unable to rollback"+ex);
 if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
 in catch block. but SQL statements executed thru. doJob1() are not rolling back.
 what might be the reason?
 thanks
 Ranganath


 Thanx Priscilla ,
 Transaction is working.
 ranganath
 "Priscilla Fung" <[email protected]> wrote:
 >
 >In your ejb-jar.xml, you should specify <transaction-type> element to
 >be "Container"
 >for container-managed transaction. If you specified it to be "Bean" for
 >bean-managed
 >transaction, EJB ontainer will suspend the caller's transaction before
 >starting
 >a new transaction for your doJobX() methods. Thus, doJob1()nd doJob2()
 >will be
 >executing in different transactions, and thus rolling back doJob2()'s
 >transaction
 >will have no effect on work done and committed in doJob1()'s transaction.
 >
 >Regards,
 >
 >Priscilla
 >
 >
 >"Ranganath" <[email protected]> wrote:
 >>
 >>
 >>
 >>I am sending config.xml,deployment descriptors, code snippet for TestSession.
 >>i
 >>am using weblogic6.0sp2.
 >>if you need any aditional info. please let me know.
 >>
 >>thanks
 >>ranganath
 >>
 >>EJB-JAR.xml
 >>
 >><?xml version="1.0"?>
 >>
 >><!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
 >JavaBeans
 >>1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
 >>
 >><ejb-jar>
 >> <enterprise-beans>
 >> <session>
 >> <ejb-name>TestSession</ejb-name>
 >> <home>com.apar.sslbridge.test.TestHome</home>
 >> <remote>com.apar.sslbridge.test.TestRemote</remote>
 >> <ejb-class>com.apar.sslbridge.test.TestBean</ejb-class>
 >> <session-type>Stateless</session-type>
 >> <transaction-type>Bean</transaction-type>
 >> <resource-ref>
 >> <res-ref-name>jdbc/oraclePool</res-ref-name>
 >> <res-type>javax.sql.DataSource</res-type>
 >> <res-auth>Container</res-auth>
 >> </resource-ref>
 >> </session>
 >> </enterprise-beans>
 >> <assembly-descriptor>
 >> <container-transaction>
 >> <method>
 >> <ejb-name>TestSession</ejb-name>
 >> <method-intf>Remote</method-intf>
 >> <method-name>*</method-name>
 >> </method>
 >> <trans-attribute>Required</trans-attribute>
 >> </container-transaction>
 >> </assembly-descriptor>
 >></ejb-jar>
 >>
 >>
 >>TestSession CODE:
 >>
 >>
 >> public void doJob1() throws RemoteException
 >> {
 >> Statement st = null;
 >> String query=null;
 >> try{
 >> con=getConnection();
 >> st=con.createStatement();
 >> query="insert into x values("+x+++")";
 >> System.out.println(query);
 >> int rec=st.executeUpdate(query);
 >> }catch(SQLException sqle)
 >> {
 >> System.out.println("SQL Exception "+sqle);
 >> throw new RemoteException("RemoteException*****SQLError");
 >> } catch (Exception e) {
 >> System.out.println("Exception "+e);
 >> throw new RemoteException("RemoteException*****GenralError");
 >> }
 >>}
 >>
 >>
 >> public void doJob2()throws RemoteException
 >> {
 >> Connection con=null;
 >> Statement st = null;
 >> String query=null;
 >> try{
 >> con=getConnection();
 >> st=con.createStatement();
 >> query="insert into y values("+x+++")";
 >> System.out.println(query);
 >> int rec=st.executeUpdate(query);
 >> }catch(SQLException sqle)
 >> {
 >> System.out.println("SQL Exception "+sqle);
 >> throw new RemoteException("RemoteException*****SQLError");
 >> } catch (Exception e) {
 >> System.out.println("Exception "+e);
 >> throw new RemoteException("RemoteException*****GenralError");
 >>}
 >>}
 >>private Connection getConnection(){
 >>try {
 >>Connection con = StaticParams.POOL_DATASOURCE.getConnection();
 >>return con;
 >> } catch(Exception e) {
 >> System.out.println("TestBean.getConnection() Unable to get get pool
 >>connection
 >>" + e);
 >> }
 >>}
 >>
 >>
 >>
 >>
 >>"Priscilla Fung" <[email protected]> wrote:
 >>>
 >>>It should work if you are using TxDataSource. Could you post your
 >config.xml,
 >>>deployment descriptors, code snippet for TestSession?
 >>>
 >>>Regards,
 >>>
 >>>Priscilla
 >>>
 >>>"Ranganath" <[email protected]> wrote:
 >>>>
 >>>>Hi,
 >>>>
 >>>> I am using UserTransaction in Stateless Session bean .
 >>>> Transaction is not rolling back.
 >>>>
 >>>>The following code is writen in stateless session bean. In UserTransaction
 >>>>i am
 >>>>calling Two methods of another stateless session bean.
 >>>> The problem is if doJob2() method fails, doJob1() method is rolling
 >>>> back. These
 >>>>two methods consist of SQL statement with different Connection Object
 >>>>from TXDataSource.And
 >>>>session bean(TestSession) is set to CMT, attribute as "Required".
 >>>>
 >>>> try{
 >>>> Context ictx=new InitialContext();
 >>>> TestHome home=(TestHome)ictx.lookup("TestSession");
 >>>> utx = sessionCtx.getUserTransaction();
 >>>> utx.begin();
 >>>> TestRemote remote=home.create();
 >>>> remote.doJob1();
 >>>> remote.doJob2();
 >>>> utx.commit();
 >>>> }catch(Exception e)
 >>>> {
 >>>> try{
 >>>> utx.rollback();
 >>>> }catch(Exception ex)
 >>>> {
 >>>> System.out.println("unable to rollback"+ex);
 >>>> }
 >>>> }
 >>>>if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
 >>>>in catch block. but SQL statements executed thru. doJob1() are not
 >>rolling
 >>>>back.
 >>>>what might be the reason?
 >>>>
 >>>>thanks
 >>>>Ranganath
 >>>
 >>
 >

Some methods not working in EJB 3.0 stateless session bean

Similar Messages

Maybe you are looking for