Problem in calling Local EJB in weblogic 7.0

Hi,
I'm calling a Local Ejb from a client application, but i'm getting the following exception
Exceptionjavax.naming.NameNotFoundException: Unable to resolve 'local' Resolved:
'' Unresolved:'local' ; remaining name 'local'
I'm Using Weblogic 7.0
But I have given the correct JNDI name in the deployment descriptor and whereever necessary
If any one knows abt this, pls reply back, its urgent
Thanks in advance
Kiran

Hi again,
The exact exception is below,
Exceptionjavax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: Invalid name:app/ejb/kmml.jar#MMLDatavalidationEJB/local-home]; Link Remaining Name: 'java:app/ejb/kmml.jar#MMLDatavalidationEJB/local-home'
thanks
kiran

Similar Messages

Challenge: call local ejb from remote ejb on weblogic 9.2

Hi ALL,
How do I call to local ejb from remote ejb object. The jar file is deployed on weblogic server 9.2, if you want get it http://geocities.yahoo.com.br/lindembe/BEAProject.jar and the source code are http://geocities.yahoo.com.br/lindembe/BEAProject.zip. It is a sample app with two ejb that works so good on JBOSS, JOnAS, but BEA Weblogic.....
The complete problem you watch http://forum.java.sun.com/thread.jspa?threadID=768718&messageID=4387570#4387570
or
http://forums.bea.com/bea/message.jspa?messageID=600043148&tstart=0

Your code in SigemFacadeBean should just do:
InitialContext ctx = new InitialContext();
when you lookup the local EJB. (This will work on all app servers. There's no need to put an app-server specific intial context factory in your code.)
Also, you can remove the jndi-name setting for the local ejb from your weblogic-ejb-jar.xml. jndi-name is only applied to remote ejbs.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Local EJBs in Weblogic 12c

Hi - We are in the process of migrating our applications from Weblogic 10.3 to 12c. Due to legacy nature of the application, it's still using EJB 2.x
Can somebody please let us know if Weblogic 12c fully supports EJB 2.x APIs and specifications. We are having some local EJBs in the code too. Would there be any potential issues migrating any local/remote EJBs or is it supposed to work out of the box?
Note: We have already gone through the article http://docs.oracle.com/cd/E24329_01/web.1211/e24446/compatibility.htm#INTRO112 and have modified our EJBs to use EJBGen annotations. We have also run our EJBs through 12c appc and it does not report any such errors.
Thanks!

I guess the local JNDI name will be visible only when you look up from the
same .ear scoped applications. It will not be visible in the global JNDI
tree (applications outside of the .ear cannot access the bean as it is
local).
I am not sure what you refer by testing via console. If you want to access
the bean from a different application (another .jar or .war which is not
part of a .ear), then you should use remote views instead of local views.
--Sathish
<Santiago Abadia> wrote in message news:[email protected]..
Hi.
There isn't any error message in the server log. It says that deployment
is sucessful.
The message that appears when I try to test the EJB in the console is:
"There was a problem determining the JNDI Name of the given bean."
Thanks

Calling remote EJB from Weblogic 8.1 to websphere 5.1

Hi, I'm trying to get a connection from my weblogic 8.1 to a EJB in a websphere 5.1
I'm connecting via IIOP without seurity, first I have a problem with the connection, in the server log appears:
java.net.UnknownHostException: remoteDNS:remoteDNS
but, it appears not at the beginning the connection, it appears when the EJB I've called, returns me the method I invoked and my weblogic didn't recognize the remote server because it have to return a DNS or IP: port and it doesn't occour, I'm not behind a FW.
Then I made modifications to the sever I register some websphere jars in the classpath but when I made this another problem become, the log shows me a message that says that the initialcontext class could not be loaded, and when I modified the classpath to recognize this the other parts of my site breakdown because their initialcontext were different.
Basically, I want some help in How to make the connection to websphere via IIOP or another protocol and what are the requeriments that I need to modify in my Weblogic, and in my class of connection.
I almost tried to make a network channel to comunicate to the websphere but it didn't work.
Can anybody give me suggestions on what to try??
Thanks

Valentin Rangel del Rosal <> writes:
I believe there is a document that describes this.
Java EE 4 interop requires that you do not need to put WebSphere
ORB/ICF classes in your WLS classpath and vice versa. You should
simply be able to make EJB refs to the remote side using an
appropriate corbaloc URL.
Can you post your EJB config and code?
andy
Hi, I'm trying to get a connection from my weblogic 8.1 to a EJB in a websphere 5.1
I'm connecting via IIOP without seurity, first I have a problem with the connection, in the server log appears:
java.net.UnknownHostException: remoteDNS:remoteDNS
but, it appears not at the beginning the connection, it appears when the EJB I've called, returns me the method I invoked and my weblogic didn't recognize the remote server because it have to return a DNS or IP: port and it doesn't occour, I'm not behind a FW.
Then I made modifications to the sever I register some websphere jars in the classpath but when I made this another problem become, the log shows me a message that says that the initialcontext class could not be loaded, and when I modified the classpath to recognize this the other parts of my site breakdown because their initialcontext were different.
Basically, I want some help in How to make the connection to websphere via IIOP or another protocol and what are the requeriments that I need to modify in my Weblogic, and in my class of connection.
I almost tried to make a network channel to comunicate to the websphere but it didn't work.
Can anybody give me suggestions on what to try??
Thanks

Problems deploying a simple EJB on Weblogic 8.1 using JDeveloper

Hey guys,
Title says it all. First I had one problem in that I could not test the connection to the Weblogic server. I moved the weblogic.jar file into the lib/ext folder and that test worked then. After that I wrote the EJB...a very simple one...and I followed the http://dev2dev.bea.com/pub/a/2006/01/wls-jdeveloper.html?page=1 tutorial so far. But when it came time to deploy the ejb to the server, I am getting this funky error:
ERROR: ejbc found errors while processing the descriptor for C:\oracle\jdeveloper\jdev\mywork\WeblogicApp\EchoEJB\deploy\ejb1.jar:
ERROR: Error from ejbc: Error processing 'META-INF/ejb-jar.xml': XML document does not appear to contain a properly formed DOCTYPE header
Honestly I am confused now...any one encounter that error?
Thanks for all replies.
Cheers

So I added the DOCTYPE and now I get another error. And that is as follows:
ERROR: Error from ejbc: Error parsing file 'META-INF/ejb-jar.xml' at line: 5 column: 219. Attribute "xmlns:xsi" must be declared for element type "ejb-jar".
It seems that when the EJB is created, then it automatically creates the appropriate ejb-jar.xml and for some reason I guess the one it is creating this time is not good enough for Weblogic because first the DOCTYPE was missing and then after inserting the DOCTYPE I am getting the above error. Any help would be appreciated. This is the first time I am using Weblogic and this is a rather disheartening amount of progress I have made since last night! ;(
Thanks in advance for any help. If I am doing something silly please point it out so I can learn!
Cheers,
Surya

RunState.Caller.Locals.ReportOptions.Directory unknown in Teststand 2013

Hello,
I have a problem due to migration between TestStand 4.1.2 and TestStand 2013.
In previous sequences I used the variables: RunState.Caller.Locals.ReportOptions.Directory, RunState.Caller.Locals.StartDate.Text, RunState.Caller.Locals.UUT.SerialNumber, RunState.Caller.Locals.ReportFilePath and others... without problem.
Now in TestStand 2013, the variables cannot be evaluated , generates an Teststand error and thus I cannot personnalize my report name and directory.
Hereafter the complete expression that cause problems:
RunState.Caller.Locals.ReportOptions.Directory=FileGlobals.Report_Directory + "\\" + RunState.Caller.Locals.StartDate.Text + "\\" + RunState.Caller.Locals.UUT.SerialNumber ,
RunState.Caller.Locals.ReportFilePath=FileGlobals.Report_Directory + "\\" + RunState.Caller.Locals.StartDate.Text + "\\" + RunState.Caller.Locals.UUT.SerialNumber + "\\" + "Report ["+ RunState.Caller.Locals.UUT.SerialNumber +"][" + Str(RunState.Caller.Locals.StartTime.Hours) +" "+ Str(RunState.Caller.Locals.StartTime.Minutes) +" "+ Str(RunState.Caller.Locals.StartTime.Seconds) + "]" + ".html",
FileGlobals.UUT_Time = "[" + RunState.Caller.Locals.UUT.SerialNumber+"][" + Str(RunState.Caller.Locals.StartTime.Hours) +" "+ Str(RunState.Caller.Locals.StartTime.Minutes) +" "+ Str(RunState.Caller.Locals.StartTime.Seconds) + "]" , FileGlobals.fileDir=RunState.Caller.Locals.ReportOptions.Directory
Thanks for your help.

If you using these expressions to set the report path and directory, then, do consider using TestStand expression to specify the report path in Report Options dialog. Its lot easier to use compared to setting values to subproperties of Runstate.Caller.Locals.ReportOptions variable.
You can get more information in the following links
http://zone.ni.com/reference/en-XX/help/370052K-01/tsref/infotopics/specifyreportfilepath_byexpressi...
http://zone.ni.com/reference/en-XX/help/370052K-01/tsfundamentals/infotopics/reports_expressions/
http://digital.ni.com/public.nsf/allkb/78E88742D0F8C3C5862576D4006B8E44
Coming to your error, please provide more information regarding which sequence file and sequence did you modify.
Also note that, in TestStand 2012, process models had major change to support plug-in architecture. Process models without the plug-in architecture (like the one used in TestStand 4.1.2) is installed in "<TestStand>\Components\Models\TestStandModels\TestStand 2010 Process Models (Legacy)" directory. If you want to migrate your process model changes, it might be valid to update the legacy process models instead of new models.
You can see brief description of TestStand 2012 process model changes in http://zone.ni.com/reference/en-XX/help/370052K-01/tshelp/infotopics/2012whatsnew/#plugin
- Shashidhar

Trying to look up a LOCAL EJB (Weblogic 8.1)

Hi,
I'm trying to look up a LOCAL EJB (Weblogic 8.1):
try
Context ct = new InitialContext();
Object o = ct.lookup("*ejbSecurityDataLocalHelper*");
catch(...)
I systematically get the following exception:
Caused by: javax.naming.LinkException: Root exception is javax.naming.NameNotFoundException: While trying to look up /app/ejb/AEX_JRK_security_EJB.jar#SecurityDataHelper/local-home in /app/ejb/ISL_MSD_mktdata_general_EJB.jar#MarketDataGeneralManager.; remaining name '/app/ejb/AEX_JRK_security_EJB/jar#SecurityDataHelper/local-home'; Link Remaining Name: 'java:app/ejb/AEX_JRK_security_EJB.jar#SecurityDataHelper/local-home'
Where SecurityDataHelper is the Local EJB, who's called from MarketDataGeneralManager EJB.
I realized that the Weblogic JNDI tree shows a red dot next to the name SecurityDataHelperLocalHome: as the other names are not red, I could guess there was something wrong at deployment... buy deployment logs are OK. When I tryied to test the EJB via the Weblogic console there was a message "The EJB SecurityDataHelper has not been tested successfully. There was a problem determining the JNDI Name of the given bean. "
My ejb-jar.xml looks like this:
<session>
<ejb-name>SecurityDataHelper</ejb-name>
<local-home>com.MyLocalHome</local-home>
<local>com.MyLocalObject</local>
<ejb-class>com.MyBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
and my weblogic-ejb-jar.xml:
<weblogic-enterprise-bean>
<ejb-name>SecurityDataHelper</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<local-jndi-name>ejbSecurityDataLocalHelper</local-jndi-name>
</weblogic-enterprise-bean>
What I am doing wrong???

Hi Dan,
As u have targeted the ConnectionFactory to "soa_server1" which is running on "realHostName:7001" ....Can u please check from the AdminConsole that the JNDI name ""jms/b2b/B2BQueueConnectionFactory" is present in the JNDI Tree?
AdminConsole---->Servers---soa_server1 (click) ---> in this general configuration page you will see a link "View JNDI Tree" please ckick on that link to see the JNDI tree entries.
If you dont see any JNDI entry there then it means there is something wrong while setting up the Connection Factory in that case please refer to the Screenshots of Creating and Targeting the Connection Factory: *http://middlewaremagic.com/weblogic/?p=1987*
Thanks
Jay SenSharma
*http://middlewaremagic.com/weblogic (Middleware magic Is Here)*

A problem determining the JNDI Name of a local EJB with WL 8.1

Hi,
I created a very simple local EJB and deployed it with Weblogic8.1. When I test
it in the Weblogic server admin page, I got the following message:
"The EJB MyLocal has not been tested successfully. There was a problem determining
the JNDI Name of the given bean."
Can anyone help figure out the problem?
Thanks
Henry

Does the ejb have a target server specified?
Does the Ejb have a Jndi binding as specified in the <local-jndi-name></local-jndi-name>
element of weblogic-ejb-jar.xml?
thanks,
Deepak
"Henry" <[email protected]> wrote:
>
>
Hi,
I created a very simple local EJB and deployed it with Weblogic8.1. When
I test
it in the Weblogic server admin page, I got the following message:
"The EJB MyLocal has not been tested successfully. There was a problem
determining
the JNDI Name of the given bean."
Can anyone help figure out the problem?
Thanks
Henry

Help-Problem in calling JMS inside an EJB having transaction attribute Required New

 Hi,
 Version wl 5.1 service pack 8
 OS - unix
 I am using a Container managed bean say Bean1(transaction attribute Required)
 which in one of its method is trying to call another EJB say Bean2 which has the
 transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
 JMS funtions coded to persist to database.JMS uses Queue connection factory and
 is an non transaction JMS session.The JMS server is running in a separate weblogic
 server and not in the server where EJB is deployed.I use the url of the JMS server
 and get the context of that server and connect my JMS.
 The problem that i am facing is
 I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
 and i can see the JMS doing the insert in the table and everthing works fine.But
 after few seconds i can see the exception/message seen on the console of the weblogic
 server where my JMS server is running as below
 Tue Sep 04 15:57:09 CDT 2001: <TX> Transaction (TxC (30486015, xid = 99963563
 2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
 .110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
 After this happen i dont see any roll back in either bean1 or bean2 or the JMS
 insert is rolled back.
 I don't know why this exception is thrown and no effects on the rollback and it
 works the way i wanted.But the only thing that keeps bothering me is the rollback
 and why does this happen.
 Thanks
 Krish.


The exception your seeing is troubling - if the tran is rolled
 back than whatever work is associated should also roll back. I suggest
 instrumenting your code to see if the tran rolling back is the same tran
 that is being used for the transactional application work that appears to succeed.
 Also, try forcing a rollback, you may see that the EJB work truly rolls back
 while the JMS work does not.
 I'm not really familiar with 5.1, but I know there is a fundamental limitation to one
 phase commits, this means that the JDBC connection pool used by JMS as well
 as that used by the EJB must be one and the same - I'm not exactly sure how
 it works, but I'm pretty sure multiple servers can share the same connection pool.
 This post seems unrelated to clustering, if you need further help, I
 suggest posting in the ejb or transaction newsgroups.
 Krish wrote:
 > Hi,
 >
 > Version wl 5.1 service pack 8
 > OS - unix
 >
 > I am using a Container managed bean say Bean1(transaction attribute Required)
 > which in one of its method is trying to call another EJB say Bean2 which has the
 > transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
 > JMS funtions coded to persist to database.JMS uses Queue connection factory and
 > is an non transaction JMS session.The JMS server is running in a separate weblogic
 > server and not in the server where EJB is deployed.I use the url of the JMS server
 > and get the context of that server and connect my JMS.
 >
 > The problem that i am facing is
 >
 > I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
 > and i can see the JMS doing the insert in the table and everthing works fine.But
 > after few seconds i can see the exception/message seen on the console of the weblogic
 > server where my JMS server is running as below
 >
 > Tue Sep 04 15:57:09 CDT 2001: <TX> Transaction (TxC (30486015, xid = 99963563
 > 2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
 > 110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
 >
 >
 > After this happen i dont see any roll back in either bean1 or bean2 or the JMS
 > insert is rolled back.
 >
 > I don't know why this exception is thrown and no effects on the rollback and it
 > works the way i wanted.But the only thing that keeps bothering me is the rollback
 > and why does this happen.
 >
 > Thanks
 >
 > Krish.

Calling Local Stateless session bean from Spring in weblogic 10.3

We are in the process of upgrading to Weblogic 10.3 from OC4J (OAS). We are using Spring and Stateless Session EJB 3 Local beans (Don't ask me why, it is decided before I came to the project).
Previously (OC4J):
-> There is no ejb-jar.xml. EJBs are configured with annotation @Stateless. No "name" or "mappedName" are defined.
Spring POJOs access EJBs by using "EJBMODULENAME_<<EJBBeanClass>>Local" as JNDI Name. I think this strange JNDI name is what OC4J assigns when there is no explicit JNDI name defined.
Sample Spring Bean configuration -
<bean name="securityEJB" class="org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean" lazy-init="true">
 <property name="jndiName">
 <value>myapp-ejb_SecurityEJBImplLocal</value>
 </property>
 <property name="resourceRef">
 <value>false</value>
 </property>
 <property name="businessInterface">
 <value>my.package.SecurityEJB</value>
 </property>
 </bean>
I understand that weblogic 10.x doesn't give any global JNDI name (JNDI tree is empty) and also looked at the blog, Link: [http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html]
So far I have tried,
1. @EJB annotation works but, I don't want to add @EJB annotations in the entire application. Since we are using Spring and EJB3, I am trying to avoid mixing them -
2. java:comp/env is supposed to work (since it is a local session bean), but it doesn't for me.
I haven't added weblogic-ejb-jar.xml as I don't think it is going to help, as there is no global JNDI name defined. Am I missing some thing?
Thx

Hi,
if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
Here is an example copied from EJB3 spec:
<ejb-local-ref>
<description>
This is a reference to the local business interface
of an EJB 3.0 session bean that provides a payroll
service.
</description>
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
<local>com.aardvark.payroll.Payroll</local>
</ejb-local-ref>
then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

Problems while performing lookup for Local EJBs

Can anybody tell me how can i perform local ejb lookup in Sun app Server 8.0/8.1 ?
I have following entries in ejb-jar.xml.
<?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 >
<enterprise-beans>
<session >
<ejb-name>TeamLeaderBean</ejb-name>
<local-home>spring.ejb.example.TeamLeaderLocalHome
</local- home>
<local>spring.ejb.example.TeamLeaderLocal</local>
<ejb-class>spring.ejb.example.TeamLeaderBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
In sun-ejb-jar.xml I have
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>TeamLeaderBean</ejb-name>
<jndi-name>TeamLeaderBeanLocal</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
In the client EJBs code I have used following ways of performing lookup...
ctx.lookup("java:comp/env//TeamLeaderBeanLocal");
ctx.lookup("java:comp/env/ejb/local/TeamLeaderBeanLocal");
ctx.lookup("ejb/TeamLeaderBeanLocal");
Unfortunately none of these performs a successful lookup...???
Can anybody solve my problem?

In order to look up a local EJB from an EJB client you have to add an <ejb-local-ref> element for client EJB. So:
<session>
<ejb-name>MyClientEJB</ejb-name>
<ejb-local-ref>
<ejb-ref-name>ejb/TeamLeaderBeanLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<ejb-link>TeamLeaderBeanLocal</ejb-link>
</ejb-local-ref>
</session>
fil
Can anybody tell me how can i perform local ejb
lookup in Sun app Server 8.0/8.1 ?
I have following entries in ejb-jar.xml.
<?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 >
<enterprise-beans>
<session >
<ejb-name>TeamLeaderBean</ejb-name>
<local-home>spring.ejb.example.TeamLeaderLocalHome
</local- home>
<local>spring.ejb.example.TeamLeaderLocal</local>
<ejb-class>spring.ejb.example.TeamLeaderBean</ejb-clas
s>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
In sun-ejb-jar.xml I have
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>TeamLeaderBean</ejb-name>
<jndi-name>TeamLeaderBeanLocal</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
In the client EJBs code I have used following ways of
performing lookup...
ctx.lookup("java:comp/env//TeamLeaderBeanLocal");
ctx.lookup("java:comp/env/ejb/local/TeamLeaderBeanLoca
l");
ctx.lookup("ejb/TeamLeaderBeanLocal");
Unfortunately none of these performs a successful
lookup...???
Can anybody solve my problem?

Timer created by EJB never triggered unless EJB called locally

Hi,
I'm using weblogic 5.1 service pack 6. JDK 1.2.2.
A call to a method of a stateless session EJB deployed on this server
sets up a Time Service trigger to perform an action only a few seconds
later.
Currently when I call this EJB method from a servlet on the same server
everything works as expected - the calls returns without error and a few
second later the trigger is set off and that action too completes
successfully.
However when I call the same EJB from a separate test program
(inside Forte), the EJB method appears to function perfectly - the
trigger appears to be set up correctly, the setServices and sheduleInit
and schedule methods of the Schedule object are all called, and the
setServices and triggerInit methods of the Trigger are both called. The
EJB method returns correctly.
However, in this case the Trigger is never activated.
Can anyone explain?
Thanks,
Richard.

Thank you very much, that did the trick.
Regards,
Rich.
Don Ferguson <[email protected]> wrote in message news:<[email protected]>...
This is just a guess, but try setting the timer to be a "Daemon", as in :
scheduledTrigger.setDaemon(true)
Probably what is happening is that the client has disconnected, and
resources associated with that client (including the timer) have been
reclaimed.
-Don
Richard Carr wrote:
Hi,
I'm using weblogic 5.1 service pack 6. JDK 1.2.2.
A call to a method of a stateless session EJB deployed on this server
sets up a Time Service trigger to perform an action only a few seconds
later.
Currently when I call this EJB method from a servlet on the same server
everything works as expected - the calls returns without error and a few
second later the trigger is set off and that action too completes
successfully.
However when I call the same EJB from a separate test program
(inside Forte), the EJB method appears to function perfectly - the
trigger appears to be set up correctly, the setServices and sheduleInit
and schedule methods of the Schedule object are all called, and the
setServices and triggerInit methods of the Trigger are both called. The
EJB method returns correctly.
However, in this case the Trigger is never activated.
Can anyone explain?
Thanks,
Richard.

Issue for the past 2 hours. Cannot make or receive calls in Little Falls, NJ. Is there a problem with the local tower?

Issue for the past 2 hours. Cannot make or receive calls in Little Falls, NJ. Is there a problem with the local tower?

You haven't enabled VoLTE (Advanced calling) have you? Not that it makes a difference just curious.
Have you upgraded to Lollipop yet?
Could be hardware or SIM card issue, read through this thread:
I can't make or take phone calls, but i can message and use data. Has this happened to anyone else? I've gone through three Samsung Galaxy S5's in the past three days, two of which have this problem and one just stopped working all together.

How do jsp call ejb in weblogic 6.0?

I put the jsp in the DefaultWebApp_Server folder and put the ejb jar file in
 the applications folder.
 I use the administrator console to deploy the ejb.
 The ejb package is 'com.test.bmp'.
 Howerver, the jsp can't import the ejb package and can't find the ejb class.
 How do the jsp call the ejb?


Any classes that are used by the JSP should be in the WEB-INF\classes
 directory. So your bean classes could be in two places if they are
 referenced in a jsp. Make sure the classes are identical.
 "Alex" <[email protected]> wrote in message
 news:[email protected]..
 > I put the jsp in the DefaultWebApp_Server folder and put the ejb jar file
 in
 > the applications folder.
 > I use the administrator console to deploy the ejb.
 > The ejb package is 'com.test.bmp'.
 > Howerver, the jsp can't import the ejb package and can't find the ejb
 class.
 > How do the jsp call the ejb?
 >
 >
 >

Problem calling deployed EJB

I've deployed an ejb but i cant seem to access it, it throws me an exception that it couldnt find a xxxHomeHelper.class which should be in the generated jar file from the deployejb utility. I have the generated file in the classpath which is why i dont understand why it throws this exception.

Hi Everybody here,
All you guys have gone too
far ahead in this EJB, but
I havent even started.
I have succesfully deployed
my EJBs in Weblogic 6. But
now I want to use Oracle's
in-built deployment tool.
Try hard as I could I could
not find a build-an-EJB-
example in the Oracle
documentation site, which
would give me a step-by-
step instruction as to how
to write the code for a
sample EJB (its home,remote
e.t.c and the code for the
client class) and how to
write out the deployment
descriptor and finally how
to deploy using the
deployejb.exe tool.
Anybody got a URL?
Thanks in advance
snodx
I HAVE POSTED THIS AS A REPLY TO SEVERAL
OTHER EJB-RELATED TOPICS HERE

Problem in calling Local EJB in weblogic 7.0

Similar Messages

Maybe you are looking for