Naming Exception Error for Session Bean (Stateless) in JDeveloper

I have written a session bean stateless in JDeveloper Environment. When i running that bean i getting the following error message.
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused:
how can we resolve this error?

http://forum.java.sun.com/thread.jsp?forum=54&thread=484437&tstart=0&trange=15
-Regards
Manikantan

Similar Messages

No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB

hi ,
i am just using EJb in my Application
just created an SessionBean and with Local interface in it i am getting this wierd exception with weblogic NetBeans and eclipse also
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
    at weblogic.ejb.container.compliance.SessionBeanClassChecker.checkInterfacesExist(SessionBeanClassChecker.java:177)
    at weblogic.ejb.container.compliance.Ejb30SessionBeanClassChecker.checkInterfacesExist(Ejb30SessionBeanClassChecker.java:27)
    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 weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:331)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
    at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:428)
    at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:437)
    at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:795)
    at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:683)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1254)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:321)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
    at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
    Truncated. see log file for complete stacktrace
>

Hi Rajendar,
I think the problem with having empty interfaces, or interfaces without methods for EJBs, is that they don't really make "sense". After deploying your EJB, a client application will use JNDI or dependency injection to access your EJB. So in your case it will look something like this
@EJB
    mytestSSBLocal myejb; //(In this case we are using the local interface)
In the second step, you will want to do something will your EJB, but since mytestSSBLocal doesn't define any methods, there is nothing you can do with your ejb.
The Exception is telling you that weblogic couldn't find a complaint interface for your EJB.
best regards, Nicolas

Naming Exception error in initiate task

Hi guys, I'm really in need of help. I'm getting naming exception error in my initiate task. There is no error code from bpel. I had copied my workflow from my development server (using oracle 10g) to my production server (using oracle 9i). I did not get this error when I'm in my development server.
The difference between these two servers are:
1) IP address
2) Oracle database version as stated above
3) domain name
The initiate task is just after setsystemdefineattribute and before my next task of sending email. The error did not halt the workflow but continue to the task of sending email.
Can someone help me? I can't seems to find the error which cause this problem.

I've found out the reason why I'm getting the naming exception error. It is due to wrong configuration in is_config.xml. I'm using Active Directory instead of JAZN and somehow I configure it wrongly to get the error.
I've switch back to JAZN XML base provider and it is working fine now but I would want to use the active directory as my identity service provider.
Currently my active directory in my production server is win2000. I'm using the is_config_for_activedirectory template but I still don't understand what values is needed to provide for the is_config.
Below are some of the items I don't understand.
1) Can I still use this if my AD is on win2k? If not, what should i use as I'm using AD as my id service provider now.
2) The default xmlns after the tag <BPMIdentityServiceConfig> do we need to change it? If so, to what values?
3) What is this property name and values after the providerType?
4) What is needed for binddn? I only know what to put for ou and dc but I'm not sure about cn.
5) What is this password for and whose password?
6) The whole lot under userControls and roleControl, I'm totally lost.
I've read through the Identity Service Provider (16.7.1) but I still can't understand how to config the active directory part.
I really hope someone could help enlighten me on this. Thanks
Hi guys, I'm really in need of help. I'm getting
naming exception error in my initiate task. There is
no error code from bpel. I had copied my workflow
from my development server (using oracle 10g) to my
production server (using oracle 9i). I did not get
this error when I'm in my development server.
The difference between these two servers are:
1) IP address
2) Oracle database version as stated above
3) domain name
The initiate task is just after
setsystemdefineattribute and before my next task of
sending email. The error did not halt the workflow
but continue to the task of sending email.
Can someone help me? I can't seems to find the error
which cause this problem.

User defined exception problem in session bean.

Hi,
I creaed one user defined exception and using this exception
in the session bean when I am trying use this bean at the client
side and cathing this exception it is not catching it properly
while server side it is throwing this exception.
I can elaborate it through client code -
try {
isModified = sessionBean1.modifyNe(Object product);
catch (ValidationException nve) {
throw nve;
catch (RemoteException remoteException) {
remoteException.printStackTrace();
server is throwing ValidationException but it is cathing in
the RemoteException.
stack trace is given below
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: com.ss.sms.common.exception.ValidationException: name should be unique
at com.sisl.snms.server.esc.common.SmsEscBean.checkDuplicateNeName(SnmsEscBean.java:56)
at com.sisl.snms.server.esc.escatm.SessionBean1.modifyNe(EscAtmBean.java:219)
at com.pramati.ejb.runtime.EscAtmBean_LocalObject_Impl_785398532._pramati_impl_modifyNe(EscAtmBean_LocalObject_Impl_785398532.java:285)
at com.pramati.ejb.runtime.EscAtmBean_LocalObject_Impl_785398532$3.run(EscAtmBean_LocalObject_Impl_785398532.java:238)
at com.pramati.security.util.JAASSecurityHelper.doAs(JAASSecurityHelper.java:158)
at com.pramati.security.util.JAASSecurityHelper.doAs(JAASSecurityHelper.java:266)
at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)

hi vikassahu
try it : remove remoteException catching. and try it with normal Exception, and make sure that Exception should be in remote interface.
and make sure that you are throwing your user Defined Excepion
ok i think this will help u
ok

Firefox stops loading files halfway through - i.e. has same settings (except allow for session) and works fine

Firefox stops loading files halfway through - Internet explorer has same settings (except allow for session), is less secure and works fine.

Do you have that problem when running in the Firefox SafeMode? 
[http://support.mozilla.com/en-US/kb/Safe+Mode] 
''Don't select anything right now, just use "Continue in SafeMode."''
If not, see this: 
[http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

Context lost for Session Beans

Hi Guys,
Using WLS4.5.1 sp13 on NT4 sp6.
We are having a problem with the Context of a Session Bean switching from the correct user to the last person who logged in. The users credentials and hence the context filter through from the JSP pages correctly and the Session Bean is created correctly.
Then when someone else logs in, both users assume the identity of the new user. The context of the EJB's being used changes to the new user for all other users.
When we do a getInitialContext() we assume the "weblogic.security.acl.Security.getCurrentUser()" properties to create the context. Either this is getting switched somehow or we are getting a circular reference to a Session Bean which is confusing weblogic.
One thing we do do is after various actions, we change the context to a new user and create a new EJB to validate against this users properties. When finished we throw this EJB away - and resume "presumably" in the original context !?!?!?
Any ideas ??!!?!?
Thankx in advance,
Andrew Harris//

I'm not sure if it is possible in 6.0, but 6.1 definitely supports this -
you can specify deployment order using console.
"Sébastien Charrier" <[email protected]> wrote:
Hi,
I was wondering if it's possible to define a deployement order for session
beans and if yes how to configure it (where in the console or in the
config.xml) ? Each session bean is in a single jar file and all the jars are
packaged in an ear file. I'm using weblogic 6.0 sp2.
thanks in advance.--
Dimitri

Validation error on retry count for session bean

Hi,
In our weblogic-ejb-jar.xml we have configured a retry count for a specific method on a local session bean. When I click on 'Browse' to select a specific method, it only shows '*' as a possible value. When we type the method name by hand, it shows a red cross next to the input field with the error 'Cannot find method "exampleMethod()" in the ExampleBean's Local interfaces'.
We use EJB 3.0 and OEPE 12.1.1.0.1 with Eclipse 3.7.2
The weblogic-ejb-jar.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://xmlns.oracle.com/weblogic/weblogic-ejb-jar"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://xmlns.oracle.com/weblogic/weblogic-ejb-jar http://xmlns.oracle.com/weblogic/weblogic-ejb-jar/1.2/weblogic-ejb-jar.xsd">
 <retry-methods-on-rollback>
 <retry-count>3</retry-count>
 <method>
 <ejb-name>ExampleBean</ejb-name>
 <method-intf>Local</method-intf>
 <method-name>exampleMethod</method-name>
 </method>
 </retry-methods-on-rollback>
</weblogic-ejb-jar>The bean looks like this:
@Stateless(mappedName = MappedName.DONNA)
@TransactionAttribute(value = TransactionAttributeType.REQUIRES_NEW)
public class ExampleBean implements Example {
}And the interface:
@Local
public interface Example {
}Does anyone else have this problem?
Thanks.
Pieter

Hi Pieter,
This is a known issue and I will keep you posted on the development.
Thanks for your feedback!
-Ram

Im getting exceptional error for website ...what is the problem for that error..error message is posted below

The initial exception that caused the request to fail, was:
com.sap.tc.useragent.UserAgentServiceException: Syntax Error in number '$4' of User-Agent Number Element ID 'engineVersion'.
at com.sap.tc.useragent.ElementTypeNumber.createElement(ElementTypeNumber.java:34)
at com.sap.tc.useragent.UserAgentElement.createElement(UserAgentElement.java:34)
at com.sap.tc.useragent.UserAgentElement.copy(UserAgentElement.java:71)
at com.sap.tc.useragent.UserAgentTemplate.instantiate(UserAgentTemplate.java:45)
at com.sap.tc.useragent.detection.RegExpDetector.detectUserAgent(RegExpDetector.java:33)
... 62 more
See full exception chain for details.
Failed to process request. Please contact your system administrator.
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
Correction Hints
Exception could be caused by the development component: com.sap.tc.useragent.interface
Note: The above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
System Environment
Client
Web Dynpro Client Type AJAX Client
User agent Mozilla/5.0 (Android; Mobile; rv:24.0) Gecko/24.0 Firefox/24.0
Client Type ff
Client Type Profile nn7
ActiveX disabled
Java Applets enabled
Accessibility mode disabled
Inline CSS n/a
Validate by rendering true
Server
Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', scV: 'sap.com', scN: 'WD-RUNTIME', location: 'SAP AG', counter: '7.3005.20130111125833.0000', R: '7.30', SP: '5', PL: '20', change number: '255333', codeline: NW730CORE_05_REL
J2EE Engine 7.30.3710.270166.20130816104554
System ID (SID) FP1
Server Node ID |13769650|137696|Server 00 01_137696|ciFP1/10.72.16.58|SERVER|RUNNING
Java VM SAP Java Server VM, version:6.1.038 19.1-b02, vendor: SAP AG
Operating system Linux, version: 2.6.32-220.el6.x86_64, architecture: amd64
Application
Java EE Application (deployable object) sap.com/pb
Web Dynpro Application PageBuilder
Request URI /webdynpro/resources/sap.com/pb/PageBuilder
Version vendor: 'sap.com', name: 'pb', scV: 'sap.com', scN: 'EP-RUNTIME', location: 'SAP AG', counter: '7.3005.20111228115104.0000', R: '7.30', SP: '5', PL: '4', change number: '160458'
Session & Other
Session Locale en_GB
Session Timezone India Standard Time
Time of Failure Sun Oct 27 09:59:27 IST 2013 (Java Time: 1382848167814)
Session User ClientUser(id=USER.PRIVATE_DATASOURCE.un:CC172020, name=CC172020)
Http Session Id 978BAO1ZCsh8JZ7REyIA575jsir4QQGyG9IA_SAP
Client Window Id WID1382848129974
Application Session Id CrXVdgZ0571vfwcUljh9Bw--Q4*zmQ0kblXVHMfCG18ZBg--
Web Dynpro Code Generation Infos
sap.com/pb
WD web module webdynpro/resources/sap.com/pb: SapDictionaryGenerationCore 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:24:28+0000, changelist=159000, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapDictionaryGenerationTemplates 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:24:57+0000, changelist=159000, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapGenerationFrameworkCore 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:14:41+0000,
WD web module webdynpro/resources/sap.com/pb: SapMetamodelCommon 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:17:37+0000, changelist=159372, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapMetamodelCore 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:15:03+0000, changelist=159372, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapMetamodelDictionary 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:20:22+0000, changelist=159002, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapMetamodelWebDynpro 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:25:40+0000, changelist=159462, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapWebDynproGenerationCore 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:37:46+0000, changelist=159461, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapWebDynproGenerationTemplates 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:37:55+0000, changelist=159461, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb: SapWebDynproRuntimeGen 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:35:55+0000, changelist=159464, host=pwdfm257, is-central=true)
sap.com/pb_api
WD (release=NW730CORE_05_REL, buildtime=2011-12-28T16:24:57+0000, changelist=159000, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapGenerationFrameworkCore 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:14:41+0000, changelist=159048, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapIdeWebDynproCheckLayer 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:37:31+0000, changelist=159461, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapMetamodelCommon 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:17:37+0000, changelist=159372, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapMetamodelCore 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:15:03+0000, changelist=159372, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapMetamodelDictionary 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:20:22+0000, changelist=159002, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapMetamodelWebDynpro 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:25:40+0000, changelist=159462, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapWebDynproGenerationCore 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:37:46+0000, changelist=159461, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapWebDynproGenerationTemplates 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:37:55+0000, changelist=159461, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/pb_api: SapWebDynproRuntimeGen 7.3005.20111228114942.0000 (release=NW730CORE_05_REL, buildtime=2011-12-28T16:35:55+0000, changelist=159464, host=pwdfm257, is-central=true)
sap.com/tc~wd~api
WD web module webdynpro/resources/sap.com/tc~wd~api: SapDictionaryGenerationCore 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:27:04+0000, changelist=159000, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapDictionaryGenerationTemplates 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:27:18+0000, changelist=159000, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapGenerationFrameworkCore 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:05:47+0000, changelist=159048, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapIdeWebDynproCheckLayer 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:39:20+0000, changelist=180142, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelCommon 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:10:50+0000, changelist=159372, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelCore 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:07:26+0000, changelist=159372, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelDictionary 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:22:41+0000, changelist=210375, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapMetamodelWebDynpro 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:27:36+0000, changelist=159462, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapWebDynproGenerationCore 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:39:36+0000, changelist=180142, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapWebDynproGenerationTemplates 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:39:43+0000, changelist=180142, host=pwdfm257, is-central=true)
WD web module webdynpro/resources/sap.com/tc~wd~api: SapWebDynproRuntimeGen 7.3005.20130109144853.0000 (release=NW730CORE_05_REL, buildtime=2013-01-11T17:37:00+0000, changelist=223591, host=pwdfm257, is-central=true)

Oh man it looks like a problem with the web server.
Its an error that happens on SAP, even my dad reported an error like this to me but i wasn't able to solve it.
What i find is that its an error with browser incompatibility,
Check this http://scn.sap.com/message/10338540

Help !! Client for session bean

I need your help for this roblem :
I have deployed a session bean in helloClient.jar and wrote TestHello class to test the session bean.
My problem ist to do this test ;i have tried with this command
java -cp HelloClient.jar TestHello ,but it works not .
Thanks.

Without source code or any description of exceptions, your problem definition is useless.

Lock Timed out exception in stateful Session Bean

Hi All,
We have a stateful session bean and put the reference of the bean in HttpSession
and retrieve it from other JSP.
While calling a method from bean, we are often getting the following exception.
Any help please?
weblogic.ejb.extensions.LockTimedOutException: Lock for primaryKey:1018581328443_46
could not be acquired without waiting.
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:134)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:447)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:159)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:487)
at com.elink.jbe.savejobses.SaveJobSesBeanEOImpl.getJobHeaderData(SaveJobSesBeanEOImpl.java:1258)
at jsp_servlet._jobentry._jbeenquirydefaults._jspService(_jbeenquirydefaults.java:243)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)

Hi Arjuna,
Thanks for your suggestions. But can you also help me how to make the session
bean thread safe?
Thanks in Advance
Srinath
"Arjuna Chala" <[email protected]> wrote:
Looks like you have two threads accessing the bean at the same time.
You
need to make it thread safe. Also, store the handle of the session bean
instead of the session bean itself in the session.
By the way, session beans (handle or otherwise) are not meant to be stored
in the HttpSession, and here is why:
http://groups.google.com/groups?q=stateful+session+bean+httpsession&hl=en&se
lm=3b72acb9%40newsgroups.bea.com&rnum=6
"srinath" <[email protected]> wrote in message
news:[email protected]...
Hi All,
We have a stateful session bean and put the reference of the bean inHttpSession
and retrieve it from other JSP.
While calling a method from bean, we are often getting the followingexception.
Any help please?
weblogic.ejb.extensions.LockTimedOutException: Lock forprimaryKey:1018581328443_46
could not be acquired without waiting.
atweblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:134)
atweblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
atweblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:447)
atweblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
t.java:159)
atweblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:487)
atcom.elink.jbe.savejobses.SaveJobSesBeanEOImpl.getJobHeaderData(SaveJobSesBea
nEOImpl.java:1258)
atjsp_servlet._jobentry._jbeenquirydefaults._jspService(_jbeenquirydefaults.ja
va:243)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:123)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:761)
atweblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:708)
atweblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:252)
atweblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)

How to implement this: Exception handler for managed bean

Hi, i'm using jdev 11g rel 1 , and i know i can use custom java class to extends DCErrorHandlerImpl, and override some method to customize the output or other info of my exceptions.
And then config it for databindings.cpx to make it available. But i found that this is only available for JboExceptions which are thrown from BC layer and through databindings.
If my exceptions are from managed bean, or just use application module to use the methods in it, while encounter exceptions, there's no way to handle it.
How can i handle it in managed bean in just one place(for architecuture layer)? ,
who can give some suggestion?

If my exceptions are from managed bean, or just use application module to use the methods in it, while encounter exceptions, there's no way to handle it.
How can i handle it in managed bean in just one place(for architecuture layer)? ,
who can give some suggestion?If you use application module methods in the managed bean, then use them through methodAction bindings so that the standard error handling works as expected.
See: http://blogs.oracle.com/smuenchadf/no_createrootappmodule_in_backing_beans.html
If you need to do a whole lot of error handling in the bean (instead of just showing a message once in a while), you might be putting too much business logic where it doesn't belong. Consider moving that logic to the AM

Exception Handling for many bean objects of a container class in a JSP page

Hello,
I have on container bean class. In this container class, there are several others class objects and the getter methods to get these objects out to the JSP pages.
I have one JSP page which will use different objects in the container class object through the getter methods of the container class.
My question is how to implement the exception handler for all the objects in the container so that the JSP page can handle all exceptions if occurrs in any object in the container?
Please give me some suggestions. Thanks
Tu

Thanks for your reply.
Since the container is the accessor class, I have no other super class for this container class, I think I will try the try catch block in the getter methods.

Execute client for Session Bean without appClient

Hi,
I want to execute a standalone client for a Session Bean in a Application Server 8 platform but I don�t want to use the "appClient" script that is used in the J2EE 1.4 Tutorial.
For example, for the Converter example I want to execute ConverterClient directly.
For this I suppose that I have to include the following lines of code:
java.util.Hashtable env = new java.util.Hashtable();
env.put( Context.INITIAL_CONTEXT_FACTORY, "XXXX" );
env.put(Context.PROVIDER_URL, "YYYY");
Context initial = new InitialContext(env);
Context myEnv = (Context) initial.lookup("java:comp/env");
BUT WHAT XXXX AND YYYY SHOULD BE IN SUN APPLICATION SERVER 8?
Thanks

When you are inside a container these are setup as properties automaticly. When you are outside the container you can setup these properties just the container does, but it is not done for you. When you use that HashTable you are giving it the properties instead of it getting them from system properties. Also, it looks like you need to change the lookup. Once you get the InitailContext you will see that you can't lookup java:comp from outside. You will have to use the fully qualified name. Something like "nodes/node1/servers/server1/ejb/myEjb". Just keep that in mind.

Remove() on EJBObect really removes associated session bean(Stateless) ?

Look at code snippet
hello.getGreetings();//hello is EJB Remote Object
hello.remove();
hello.getGreetings();//This shouldn't work ... But it is giving me greeting message

Look at code snippet
hello.getGreetings();//hello is EJB Remote Object
hello.remove();
hello.getGreetings();//This shouldn't work ... But it
is giving me greeting messageNo, of course you cannot delete an instance of stateless bean.
It's because they live in a pool and only EJB container decides when to create or delete bean instances.

EJB3 - More than one remote interface for Session Bean?

Hi,
Is it possible in EJB3 to have more than one remote interface for a SessionBean?
I have seen it posetd on here that it is possible but never been able to find any other information.
Using JBoss as my App Server, I have deployed an App, where a SessionBean is defined as implementing 2 interfaces, both of which are annotated using @remote.
However when I examine the JBoss JMX Console, Global JNDI Namespace only one remote interface is listed, and indeed it is the first one defined in the SessionBean.
Considering I use a String similar to (MyApp/MyBean/remote) to do the JNDI lookup, this would indicate that it is not possible to have more than one remote interface.
1. Is this a JBoss specific limitation?
2. Is there another way of performing the JNDI lookup?
Thanks,
Alan.

Hi,
Thanks for prompt response! I tried the suggestion in my application, and the output from JBoss JMX Console was
+- XXXBean (class: org.jnp.interfaces.NamingContext)
| | +- remote (proxy: $Proxy291 implements No ClassLoaders found for: xxx.xxx.xxx.xxx.xxx.Remote1 (no security manager: RMI class loader disabled))Again only displaying the remote interface that is first in the @remote ({ Remote1.class , Remote2.class}) list. This would lead me to believe that JBoss does not support this.
Can anyone confirm this?
Alan.

Naming Exception Error for Session Bean (Stateless) in JDeveloper

Similar Messages

Maybe you are looking for