Warning during javac

Hi,
I am sorting a Vector that contains CardTiles objects. CardTiles is a class that extends JButton and implements Comparable. The code works fine but i get the following warning after compilation.
Note: DeckOfCards.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
After compiling with -Xlint, i get the following warning;
DeckOfCards.java:173: warning: [unchecked] unchecked method invocation: <T>sort(java.util.List<T>) in java.util.Collections is applied to (java.util.Vector<CardTiles>)
Collections.sort(handTwo);
^
What could be the problem? Is Collections.sort() only intended for Collections of type List?
Many thanks!

I am sorting a Vector that contains CardTiles objects. CardTiles is a class that extends JButton and implements Comparable.Can you show us how you are declaring the CardTiles class and the Vector variable.
Thanks!
PS: The first thread which changed places 3 times!

Similar Messages

Compile-time warning during javac of a Class that implements Comparable

Hello All,
I have defined a class as follows;
public class CardTiles extends JButton implements Comparable{
During normal compilation with javac, it tell me to use Xlint to compile and the warning it throws is below:
CardTiles.java:4: warning: [serial] serializable class CardTiles has no definition of serialVersionUID
public class CardTiles extends JButton implements Comparable{
^
1 warning
What does this warning mean?
Many thanks!

ejp wrote:
you can choose to to differentiate between various versions of your CardTiles classThat's back to front. Serialization will always do that unless you stop it, which you can do via a fixed serialVersionUID. This tells Serialization that different versions of your class are compatible under serialization.I suppose I see it this way because I wouldn't have a serializable object without an ID. Without having an explicit ID the process isn't as transparent to me. It's the same sort of thing as using braces for statements when they're not necessary, e.g.
          if(check)
               System.out.println("check is on");
          else
               System.out.println("check is off");     versus
          if(check) {
               System.out.println("check is on");
          } else {
               System.out.println("check is off");
          }

MacBook shuts down without warning during calibration (39% battery power)

My MacBook has been shutting down without warning during recent calibrations (which I've done approximately every two months). Most recently it shut down after 2 hours and 20 minutes on battery power with a battery reading of 39% -- i.e., nowhere close to the 0% of a fully rundown battery.
The result is that:
I'm not seeing the 'low battery' warning dialog before the computer shuts down; and
(ii) I'm not able to save current work and close all applications when the battery's charge gets low, before the computer goes to sleep (because it just shuts down without warning)
Can I do anything about this? Is it just an unavoidable indication of declining battery performance?
My MacBook is 15 months old. Current 'battery information' is listed below.
Thanks. Replies appreciated.
Battery Information:
Battery Installed: Yes
First low level warning: No
Full Charge Capacity (mAh): 4792
Remaining Capacity (mAh): 4790
Amperage (mA): 0
Voltage (mV): 12477
Cycle Count: 23
------------------------------

stevenray1 wrote:
1. I'm not sure how to match the path you listed re: the '1.3 battery update' to what's on my MacBook. Maybe I just don't understand how to interpret it, but I don't have a root folder (or any other folder) identified as 'MacBook.' When I used Spotlight, I also didn't come up with a BatteryUpdater.bundle. A file named BatteryUpdate2007001.pkg was all that Spotlight turned up.
On my MacBoook my hard drive that I boot from is named Mort's MacBook. Yours may be similar I don't know. It is the drive you boot from. Mines shows in finder as the top level drive. The next level in column view. Then you find the System file and go from there.
If your not sure what you named your drive or which one it is click the apple in the upper left corner and then pick *About This Mac* You then should see *Startup Disk* and next to that the name is what you refer too when you look for the folder path I gave.
2. You recommended resetting the SMC. However, the info file you provided a link for says it shouldn't be "necessary except as a last resort in cases where a hardware failure of the power management system is suspected." Does that accurately describe the condition I reported? Also, the problems listed as possible reasons to reset the SMC don't include the one I posted about.
The reason I suggest resetting the SMC is that your changing one of the components that is controlled by the functions of the SMC. The battery is a big part of the system which the battery update changes. To get it to be sure to recognize the new bundle you reset the SMC. The instructions linked are not all inclusive but if you don't want to reset it that is up to you.
3. Similarly, re: the 1.2 Battery Update, it's not clear to me that any of the listed 'symptoms' of a faulty battery apply in my case -- unless what I reported indicates a "+low charge capacity/runtime+." Does it?
The battery update instructions are again not all inclusive. If you don't want to do it that is fine. All I know is you have a MacBook Pro update installed at the moment. You don't have a MacBook Pro. This suggestion of mine has helped many people with problems as reported by you. You do not have to do anything you don't want. That is your choice. Is your battery cutting off at 39% considered normal operating or capacity to you? I personally would call it a faulty battery, but thats just me.
What would be your definition of a faulty battery?
4. Apparently, you had a faulty battery which Apple replaced. I wasn't sure from your message whether you had other things going on that made it clear you had a faulty battery, or only the same symptoms I reported. Were there other power-related problems in your case, or only, as you wrote "the same thing as yours except mine cut off at 28%"?
I guess I misunderstood your original post, everything yours was doing mine was doing except mine cut off at 28% not 39%. I can only give advice on what you post. Are there other things happening that you didn't mention?
My idea of a faulty battery must be different than yours. If I don't get warnings I should and the battery does not work like it used to then that is a faulty battery in my opinion.
If your not comfortable with any of my suggestions contact Apple support and maybe they can help you. Possibly one of the other posters on here can give you different advice that you agree with. Never do anything advised in the forums unless you agree with it.

-200361 warning during DAQmx acquisition

Hello,
I have been getting this warning during acquistion with 6255 OEM. This interrupts the continous data acquisiton of my software. I have tried reducing the sampling rate but doesn't help. Can some one help me find the way of handling this situration in my program to avoid the interruption in the continous data acquistion?
Thanks.

MansoorEE wrote:
This program works fine when I am using a simple USB cable. But, now I am requried to use a USB extender with 100m long Ethernet cable. It works fine for a while; but at some point this warning occurs and acquisition stops.
That sounds like you were working on the hairy edge before and now that the communication bus is likely just a little bit slower due to the conversion, you fail.
Try setting your loop to run a little bit faster, like maybe 100ms. By reading the samples faster, you are less likely to reach your buffer limit.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Aggregate storage cache warning during buffer commit

h5. Summary
Having followed the documentation to set the ASO storage cache size I still get a warning during buffer load commit that says it should be increased.
h5. Storage Cache Setting
The documentation says:
A 32 MB cache setting supports a database with approximately 2 GB of input-level data. If the input-level data size is greater than 2 GB by some factor, the aggregate storage cache can be increased by the square root of the factor. For example, if the input-level data size is 3 GB (2 GB * 1.5), multiply the aggregate storage cache size of 32 MB by the square root of 1.5, and set the aggregate cache size to the result: 39.04 MB.
My database has 127,643,648k of base data which is 60.8x bigger than 2GB. SQRT of this is 7.8 so I my optimal cache size should be (7.8*32MB) = 250MB. My cache size is in fact 256MB because I have to set it before the data load based on estimates.
h5. Data Load
The initial data load is done in 3 maxl sessions into 3 buffers. The final import output then looks like this:
MAXL> import database "4572_a"."agg" data from load_buffer with buffer_id 1, 2, 3;
OK/INFO - 1270041 - For better performance, increase the size of aggregate storage cache.
OK/INFO - 1270041 - For better performance, increase the size of aggregate storage cache.
OK/INFO - 1270041 - For better performance, increase the size of aggregate storage cache.
OK/INFO - 1003058 - Data load buffer commit elapsed time : [5131.49] seconds.
OK/INFO - 1241113 - Database import completed ['4572_a'.'agg'].
MAXL>
h5. The Question
Can anybody tell me why the final import is recommending increasing the storage cache when it is already slightly larger than the value specified in the documentation?
h5. Versions
Essbase Release 11.1.2 (ESB11.1.2.1.102B147)
Linux version 2.6.32.12-0.7-default (geeko@buildhost) (gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) ) #1 SMP 2010-05-20 11:14:20 +0200 64 bit

My understanding is that storage cache setting calculation you quoted is based on the cache requirements for retrieval. This recommendation has remained unchanged since ASO was first introduced in v7 (?) and was certainly done before the advent of parallel loading.
I think that the ASO cache is used during the combination of the buffers. As a result depending on how ASO works internally you would get this warning unless your buffer was:
1. = to the final load size of the database
2. OR if the cache was only used when data existed for the same "Sparse" combination of dimensions in more than one buffer the required size would be a function of the number of cross buffer combinations required
3. OR if the Cache is needed only when compression dimension member groups cross buffers
By "Sparse" dimension I mean the non-compressed dimensions.
Therefore you might try some experiments. To test case x above:
1. Forget it you will get this message unless you have a cache large enough for the final data set size on disk
2. sort your data so that no dimensional combination exists in more than one buffer - ie sort by all non-compression dimensions then by the compression dimension
3. Often your compression dimension is time based (EVEN THOUGH THIS IS VERY SUB-OPTIMAL). If so you could sort the data by the compression dimension only and break the files so that the first 16 compression members (as seen in the outline) are in buffer 1, the next 16 in buffer 2 and the next in buffer 3
Also if your machine is IO bound (as most are during a load of this size) and your cpu is not - try using os level compression on your input files - it could speed things up greatly.
Finally regarding my comments on time based compression dimension - you should consider building a stored dimension for this along the lines of what I have proposed in some posts on network54 (search for DanP on network54.com/forum/58296 - I would give you a link but it is down now).
OR better yet in the forthcoming book (of which Robb is a co-author) Developing Essbase Applications: Advanced Techniques for Finance and IT Professionals http://www.amazon.com/Developing-Essbase-Applications-Techniques-Professionals/dp/1466553308/ref=sr_1_1?ie=UTF8&qid=1335973291&sr=8-1
I really hope you will try the suggestions above and post your results.

Change error message to warning during pricing condition upper limit check.

Hi All,
I have a header condition ZFMN to which maximum amount that can be entered is set to $5000. When I enter the amount greater than this, it gives me error message.
Could we change it to warning message?

During Creation of PO when you click PO Check, What Include you are using.
Cann't you use the BADI ME_PROCESS_PO_CUST and write the code whatever you want in PO_CHECK,
There during Check you use any FM POP_TO_CONFIRM OR POP_TO_INFORM or show any information Message too.
Try it once.
Thanks
Arbind

SOLUTION to iPhoto 6 crashing without warning during library upgrade

THE PROBLEM
The problem which I and some others in this forum were facing was that iPhoto 6 would CRASH WITHOUT WARNING halfway through the process of updating our previous iPhoto 5 library. This is a different problem from the permissions issues which some other users have faced, which iPhoto 6 does warn you about.
THE EXPLANATION
After trial and error, I concluded that there was a corrupted photo in my library that iPhoto was choking on during the upgrading process. Unfortunately, there was no easy way to identify which of my 3000+ photos this was. Hence, the solution was to laboriously test my library year-by-year, to isolate the year in which the problematic photo was hiding. This meant creating individual copies of my iPhoto library, one for each year, and then test-upgrading each individual copy. Each individual year upgraded fine, except for 2004. Thus, I could deduce that the problematic photo was in 2004. I then created a new copy of my iPhoto 5 library, containing all photos except for those in 2004. It upgraded fine. I then manually dragged my photos from 2004 back into iPhoto. Thus, all my comments/ratings/keywords for other years were intact, and I only had to re-do 2004.
THE STEPS
In order to use this solution, you must have a backup of your iPhoto 5 library. It also helps if you can install a fresh copy of Mac OS X 10.4 and iPhoto 6 (SIX) on another partition. The steps are:
1. Reinstall/'downgrade' to iPhoto 5 (this requires deleting the iPhoto 6 application and also all iPhoto receipts in the /Library/Receipts folder, before reinstalling from iLife '05)
2. Create multiple copies of your iPhoto 5 library backup (the entire iPhoto Library folder from your iPhoto 5), and title the backup copies 'Early Photos', '2003', '2004', '2005' and '2006'.
3. By holding down Option while launching iPhoto 5, open each copy of your library, and delete photos from each copy so that only one year of photos remains in each copy, i.e. you should have one library containing only 'Early Photos' (pre-2003), one containing only 2003 photos, etc.
4. Test-upgraded each individual 'annual' library on another installation of iPhoto 6. Those that can be upgraded are fine. The one that crashes obviously contains the corrupted photo.
5. Go back and create a fresh copy of your iPhoto 5 library, and open it in iPhoto 5. Delete only the photos from the problematic year, leaving all the rest behind. Before deleting the photos, drag them into a folder on the desktop, so that you can re-import them later.
6. Now re-install iPhoto 6 (the end is near, trust me) and open the fresh copy of your iPhoto 5 library. Upgrade it. You will now have a upgraded library, minus all the photos from the excluded year.
7. You should now be able to re-import photos from the excluded year, by dragging them into iPhoto 6. However, this may mean reintroducing the corrupted photo into your library. I really can't help you beyond this - re-import at your own risk, and always keep backups.
8. Enjoy (after much frustration).
ALTERNATIVES
It isn't necessary to test your library year-by-year. For example, if you only have photos from one year, then you'd have to find some other way to break your library into logical chunks, and test each chunk using the procedure above. Again, the chunk that crashes during upgrading contains the corrupted photo. It's really up to you how finely you want to sub-divide and test your iPhoto 5 library, to isolate the corrupted photo.
(P.S. Really, this should be addressed by Apple. It is murder and really tedious to do this, and I suspect it would be difficult for anyone not familiar with Mac OS X, and also difficult if you don't have multiple partitions/drives to install separate copies of iPhoto 5 and iPhoto 6.

Thanks for your help. It should work with some iPhoto libraries, but unfortunately not with mine.
iPhoto was crashing, so I found the guilty album, deleted it, retried: but it crashes on another album, etc. I think I have more than one corrupted picture/album, so the only solution to make iPhoto complete the update was to remove 90% of my pictures... not a real solution

Exclusively locked files warning during startup on my A100 Satellite

I get a warning about (at least?) 2 exclusively locked files occuring during startup. How do I identify them and how do I "unlock" them? I am not going to ask how they got exclusively locked.
I have tried updating the bootup file but I'm told by the updater that my bootup file is identical to the update.
I have done a complete Vipre scan which has pronounced my laptop to be clean.
Thnaks,
John

Which Satellite A100, John? What's the part number?
Which Windows?
Please quote the precise message you get on startup. Put it on a line by itself. No paraphrasing. Spelling counts.
-Jerry

OOB warning during IPS 4260 signature update via CSM

Hi,
During the recent IPS signatures updates via CSM, i have noticed that there was warning (below).
>OOB change detected - Out of Band(OOB)and sensor configuration change happened on device. But you selected to continue deployment in case of OOB. Continuing...
what is the cause & impact of such event?
As i suspected there is a mismatch of configuration, my inline interfaces are no longer applied to the virtual sensor 'VS0'. Could it be due to the mis-synchronisation?
Apprepriate for any advice.
thanks
cash

CSM keeps an internal copy of the configuration it last pushed to the sensor.
Each portion of the configuration has a configToken assigned to it by the sensor. The config token is a base 64 encoding of that configuration portion.
Each time CSM goes to push a new configuration it will compare the configToken of it's previously saved configuration for that sensor against the configToken of the configuration currently on the sensor.
If the 2 configTokens match, then no configuration change has been made since the last time that CSM pushed a configuration to the sensor. CSM can safely push the new configuration to the sensor.
If the 2 configTokens do not match, then an Out Of Band (OOB) configuration change has been made to the sensor. This means that the sensor's configuration has been modified by something other than CSM. This may have been a user changing something through the CLI or IDM instead of using CSM.
In these situations CSM gives you the option of either stopping the push of the new configuration so the detected changes can be imported and evaluated by the user, or to go ahead and push the changes to the sensor.
If you decide to go ahead and push the changes to the sensor, the outcome of the configuration change is not guaranteed.
The sensor may wind up merging the OOB changes in with the new configuration from CSM, or the CSM changes may wind up overwriting the OOB changes.
So telling CSM to push the new configuration even when OOB changes have been detected can be risky and can cause loss of some of your configuration.
I fyou will be making changes with CLI or IDM, then it is always best to import those changes into CSM before making further configuration changes in CSM.

Warning during check table

hi everyone,
i create a new table and then check it, a warning like below will appear,"TABLES IS NOT YET CLASSIFIED". What will cause that? Any suggestion is appreciated.
Regards,
Julian

Hi,
"TABLES IS NOT YET CLASSIFIED".
this is because you have not classified your table
from menu EXTRAS->ENHANCMENT CATEGORY
now choose the one of the radio button ans press ok.
read the documentation of ENHANCEMENT CATEGORY also.
DE DE_RADIO_EXCLASS
Short Text
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the categorycannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.
Regards
vijay

IPhone ~needs~ an AUDIBLE Battery-low warning during calls!!!

Okay, I've been needing to do this for quite some time. I'm actually surprised to find no one else has made this complaint yet (that I've been able to find).
I am absolutely sick and tired of my iPhone dying in the middle of a call because I was not alerted to the battery's status once it got to 20% or lower.
Does it make sense to anyone else that this happens? You're on a call, to your knowledge the battery was full or reasonably full before but now that you're talking you can't see the screen and you're not thinking about it so you keep talking. A while later your call drops and as you start to curse AT&T once again for the miserable coverage & constantly dropping calls you see that it's not them after all, but your phone's dead battery.
Come on Apple.... How hard can it possibly be to program in an AUDIBLE-IN-CALL alert that tells you that your battery is about to die. This is so basic and simple that I'm finding it hard to believe that this hasn't been addressed before now!!! Don't get me wrong, I love my iPhone. I will never need another phone as long as there is some variation of the iPhone in existence. But seriously, this is something that should have been dealt with AGES AGO.
I don't feel like I should even have to be saying this, but when you are in a call, your phone is against your ear, or if you use a headset of some kind, your phone is likely in a pocket. A Battery-Low warning that comes up on the screen is NOT going to be visible. There NEEDS to be a way for the iPhone to notify the user of a Battery-Low status that ACTUALLY GETS THEIR ATTENTION, not simply to remind them AFTER they've got it charging again that, yes, now that the phone is charging and back up from 0%, that the battery is still in-fact below 20%....
I really am a reasonably devoted Apple fan, but I am highly annoyed by this, because while I have had my iPhone 3G since the week they were released, whenever the above problem would happen to me I just assumed it would only be a matter of time before it got ironed out. I mean, come on, Apple's a smart company, and this is such a basic thing that lesser phones have had this programmed into their OS's going back to some of the very first cellular phones in existence, I know, I've owned a few.
Apple, Please. Fix this.
Thank you in advance.

thegadson6 wrote:
I just posted the same thing and it's now 2014!!!! I have endured this problem since my iphone 3gs.
And the option is still the same. Give feedback to Apple directly at www.apple.com/feedback.
Nothing anyone can do here, other than recommend that you be more aware of your battery life. Keep it connected to a power source when not in use, or if one is readily available when you are using it. I have a charger for home, one for my car, and one at work. I never see the battery low indicators, except in very rare cases. It's very rare for my battery to be below 50%.

Warning during maintenance of IT0008

Hi All,
When i try to maintain Basic salary in IT0008, i get a warning "Basic Salary is not a part of the Pay Components".
Could anybody guide as to what is wrong and where?

Hi Muthu,
Thanx for your reply.
Emp Group in IT0000 was in place. However, the position assigned was incorrect and hence the warning was in display. Now the warning has been taken care of but IT0008 is giving run time error "WRITE_TO_OFFSET_TOOLARGE"
Error analysis
In a "WRITE src TO dest+off[(len)] [INDEX i]" statement, "off" contains a target field offset (3) which is larger than the length of the target field "dest" (4). This is not allowed.
Any clues??

Annoying email setup warning during roaming on 580...

Guys,
Does anyone know how to disable the message that pops up from the Email Setup program when the network changes (e.g.. During roaming) on the Nokia 5800 (FW version 50.0.005) saying "allow phone to use network to send and receive data".
Basically if you go abroad and have roaming enabled you will often find the phone changes network, e.g.. I was just in Italy and it regularly roamed from Vodafone IT to I Wind and TIM. Each time it swapped network I got the email setup program displayed and it said "can it use the network" which required a response. Why?? No other application needs this constant interaction!
It was especially annoying as I would be using the sat nav (so cool) but then while driving it would change network, then this message would be displayed which takes the focus from Ovi Maps so the screen blacks out, and locks (which seemed to stop the navigation instructions being read out even!).
Please fix this Nokia!!!

Any update on this from Nokia?
I recently updated my 5800xm and I have the same problem now; in fact I wouldn'st say roaming changes anything, it happens all the time.
I really like all the updates we get on the 5800; I think it adds a lot of credibility to the Nokia offering.
But this bug should be resolved now. The only solution I have is to remove the mail setup application; not really a solution is it?
Or I could disable it. Any idea how to disable an app on NOkia 5800?

Warning during metadata loading to hyperion planning

Hi,
Hi,
When I do the mapping even if it is successful and the data is populated in the dimension(Eg. In this case for Business Dimension) I am still getting this warning:
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 2, in ?
Planning Writer Load Summary:
Number of rows successfully processed: 0
Number of rows rejected: 1018
at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
at com.sunopsis.dwg.cmd.e.i(e.java)
at com.sunopsis.dwg.cmd.g.y(g.java)
at com.sunopsis.dwg.cmd.e.run(e.java)
at java.lang.Thread.run(Unknown Source)
The no of rows successfully processed is always zero even if it is getting populated. Please help.
Regrards,
VINAY

You set up the logging like this - http://1.bp.blogspot.com/__2AaArK5lW8/SN-G7H6f6TI/AAAAAAAAAd4/Ovyj1GK-dKk/s1600-h/25.png
It will write the output to two logs that are text format and can be opened.
Cheers
John
http://john-goodwin.blogspot.com/

"GConf-WARNING **" during update

Hello.
A few moments ago, when I typed pacman -Syyu I got this warning (in bold) that I don't know its meaning and how to resolve it:
[ppsalama@PEPE ~]$ sudo pacman -Syyu
[sudo] password for ppsalama:
:: Sincronizando las bases de datos de paquetes...
core 108,1 KiB 335K/s 00:00 [##########################################] 100%
extra 1565,5 KiB 1005K/s 00:02 [##########################################] 100%
community 2,1 MiB 1054K/s 00:02 [##########################################] 100%
archlinuxfr 12,2 KiB 185K/s 00:00 [##########################################] 100%
:: Iniciando actualización completa del sistema...
:: ¿Reemplazar kdenetwork-kdnssd con extra/kdenetwork-zeroconf-ioslave? [S/n] s
resolviendo dependencias...
verificando conflictos...
Paquetes (9): farstream-0.1-0.1.2-4 ghostscript-9.14-1 groff-1.22.2-6 gstreamer0.10-good-plugins-0.10.31-5
kdenetwork-kdnssd-4.12.3-1 [quitando] kdenetwork-zeroconf-ioslave-4.12.4-1 linux-3.13.8-1
linux-docs-3.13.8-1 linux-headers-3.13.8-1
Tamaño Total de Descarga: 74,39 MiB
Tamaño Total Instalado: 189,57 MiB
Tamaño neto a actualizar: 25,93 MiB
:: ¿Continuar con la instalación? [S/n] s
:: Recuperando paquetes ...
groff-1.22.2-6-i686 1735,6 KiB 1014K/s 00:02 [##########################################] 100%
linux-3.13.8-1-i686 49,5 MiB 1114K/s 00:45 [##########################################] 100%
linux-docs-3.13.8-1-i686 4,2 MiB 1168K/s 00:04 [##########################################] 100%
linux-headers-3.13.8-1-i686 5,9 MiB 985K/s 00:06 [##########################################] 100%
gstreamer0.10-good-plugins-0.10.31-5-i686 307,0 KiB 307K/s 00:01 [##########################################] 100%
farstream-0.1-0.1.2-4-i686 206,3 KiB 1086K/s 00:00 [##########################################] 100%
ghostscript-9.14-1-i686 12,6 MiB 1184K/s 00:11 [##########################################] 100%
kdenetwork-zeroconf-ioslave-4.12.4-1-i686 22,9 KiB 1274K/s 00:00 [##########################################] 100%
(8/8) verificando llaves en el llavero [##########################################] 100%
(8/8) verificando la integridad de los paquetes [##########################################] 100%
(8/8) cargando los archivos del paquete... [##########################################] 100%
(8/8) verificando conflictos entre archivos [##########################################] 100%
(9/9) verificando el espacio disponible en disco [##########################################] 100%
(1/1) quitando kdenetwork-kdnssd [##########################################] 100%
(1/8) instalando gstreamer0.10-good-plugins [##########################################] 100%
(gconftool-2:3388): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
(2/8) actualizando farstream-0.1 [##########################################] 100%
(3/8) actualizando ghostscript [##########################################] 100%
(4/8) actualizando groff [##########################################] 100%
(5/8) instalando kdenetwork-zeroconf-ioslave [##########################################] 100%
(6/8) actualizando linux [##########################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.13.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.13.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
(7/8) actualizando linux-docs [##########################################] 100%
(8/8) actualizando linux-headers [##########################################] 100%
[ppsalama@PEPE ~]$
Any suggestions for what to do?
Thanks

I've checked, and if i run 'sudo pacman -S gstreamer0.10-good-plugins' from a teminal in X, there's no error.
Below are the contents of gstreamer0.10-good-plugins.install file, it does seem that the gconfpkg command is giving this error when run outside of X.
Seems we have a "bug" in the gstreamer0.10-good-plugins package.
pkgname=gstreamer0.10-good-plugins
post_install() {
usr/sbin/gconfpkg --install ${pkgname}
pre_upgrade() {
if [ -f usr/share/gconf/schemas/${pkgname}.schemas ]; then
pre_remove
fi
post_upgrade() {
post_install
pre_remove() {
usr/sbin/gconfpkg --uninstall ${pkgname}
Last edited by Lone_Wolf (2014-04-07 11:31:41)

Warning during javac

Similar Messages

Maybe you are looking for