• Post Reply Bookmark Topic Watch Topic
  • New Topic

weblogic7.0. simple SS-Bean

 
manju latha
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
what could be the problem for the below exception
which occured in weblogic7.0 server when i run simple
statelessSession bean..???
(sorry for showing u big description(exception ))

java.io.IOException: The filename, directory name, or volume label syntax is incorrect
Start server side stack trace:
java.io.IOException: The filename, directory name, or volume label syntax is incorrect
at java.io.Win32FileSystem.canonicalize(Native Method)
at java.io.File.getCanonicalPath(File.java:435)
at weblogic.management.deploy.DeployerRuntime.validatePath(DeployerRuntime.java:780)
at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:319)
at weblogic.management.deploy.DeployerRuntime.access$0(DeployerRuntime.java:282)
at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:947)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:941)
at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:279)
at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:272)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:717)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:699)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:921)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:359)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:762)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
End server side stack trace

<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.Management
 
Dave Landers
Ranch Hand
Posts: 401
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That message is not very helpful, is it?
My guess would be that the Path for the Application element in config.xml is wrong. (You will have an Application even if you just deployed an EJB).
You can look at config.xml and see if it looks right, or start the server and check the Path for the Application or EJB in the console (or just delete it and deploy it again).
The Path should point to one of these (depending on what you have):
- the EAR file for your app
- the directory for the "exploded ear"
- the directroy that contains the ejb-jar file
 
John Fontana
Ranch Hand
Posts: 235
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I recently got that error message while creating a new web application. I was truly baffled.
As it turns out, some items in the directory were read-only. If you are using Windows, check the properties and make sure that read-only is unchecked.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!